From: "Darrick J. Wong" <djwong@kernel.org>
To: djwong@kernel.org
Cc: Christoph Hellwig <hch@lst.de>,
Chandan Babu R <chandanrlinux@gmail.com>,
Brian Foster <bfoster@redhat.com>,
linux-xfs@vger.kernel.org, hch@infradead.org,
chandanrlinux@gmail.com, bfoster@redhat.com
Subject: [PATCHSET v2 0/3] xfs: various small fixes and cleanups
Date: Fri, 18 Jun 2021 11:53:53 -0700 [thread overview]
Message-ID: <162404243382.2377241.18273624393083430320.stgit@locust> (raw)
Hi all,
I found a couple of small things that looked like they needed cleaning
while debugging other problems in my development tree.
v2: more cleanups for shutdown messaging
If you're going to start using this mess, you probably ought to just
pull from my git trees, which are linked below.
This is an extraordinary way to destroy everything. Enjoy!
Comments and questions are, as always, welcome.
--D
kernel git tree:
https://git.kernel.org/cgit/linux/kernel/git/djwong/xfs-linux.git/log/?h=random-fixes-5.14
---
fs/xfs/xfs_fsops.c | 16 ++++++++--------
fs/xfs/xfs_icache.c | 8 ++++----
fs/xfs/xfs_icache.h | 6 +++---
fs/xfs/xfs_trace.h | 4 ++--
4 files changed, 17 insertions(+), 17 deletions(-)
next reply other threads:[~2021-06-18 18:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 18:53 Darrick J. Wong [this message]
2021-06-18 18:53 ` [PATCH 1/3] xfs: fix type mismatches in the inode reclaim functions Darrick J. Wong
2021-06-20 22:23 ` Dave Chinner
2021-06-18 18:54 ` [PATCH 2/3] xfs: print name of function causing fs shutdown instead of hex pointer Darrick J. Wong
2021-06-20 22:24 ` Dave Chinner
2021-06-21 4:41 ` Chandan Babu R
2021-06-21 5:26 ` Christoph Hellwig
2021-06-18 18:54 ` [PATCH 3/3] xfs: shorten the shutdown messages to a single line Darrick J. Wong
2021-06-20 22:29 ` Dave Chinner
2021-06-21 4:41 ` Chandan Babu R
2021-06-21 5:30 ` Christoph Hellwig
2021-06-21 6:02 ` Dave Chinner
2021-06-21 6:06 ` Christoph Hellwig
2021-06-21 6:29 ` Dave Chinner
2021-06-21 16:56 ` Darrick J. Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=162404243382.2377241.18273624393083430320.stgit@locust \
--to=djwong@kernel.org \
--cc=bfoster@redhat.com \
--cc=chandanrlinux@gmail.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=linux-xfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.