From: Christian Brauner <brauner@kernel.org>
To: Jan Kara <jack@suse.cz>
Cc: Al Viro <viro@zeniv.linux.org.uk>, Christoph Hellwig <hch@lst.de>,
Miklos Szeredi <miklos@szeredi.hu>,
Amir Goldstein <amir73il@gmail.com>,
linux-fsdevel@vger.kernel.org, kernel test robot <lkp@intel.com>,
Dan Carpenter <dan.carpenter@linaro.org>
Subject: Re: [PATCH 0/2] fs: rename follow-up fixes
Date: Tue, 4 Jul 2023 10:14:47 +0200 [thread overview]
Message-ID: <20230704-dankbar-zweihundert-c8b44d516e2a@brauner> (raw)
In-Reply-To: <20230703162321.qqte5msavuijnu4l@quack3>
On Mon, Jul 03, 2023 at 06:23:21PM +0200, Jan Kara wrote:
> Hello Christian!
>
> On Mon 03-07-23 16:49:10, Christian Brauner wrote:
> > Two minor fixes for the rename work for this cycle. First one is based
> > on a static analysis report from earlier today. The second one is based
> > on manual review.
>
> Thanks! In fact I've sent you a very same patch as patch 1 just a while ago
> [1] and your patch 2 already back in June [2]. But feel free to use your
> fixups, they look good to me so also feel free to add:
>
> Reviewed-by: Jan Kara <jack@suse.cz>
I'll take yours and just massage the commit message. :)
next prev parent reply other threads:[~2023-07-04 8:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 14:49 [PATCH 0/2] fs: rename follow-up fixes Christian Brauner
2023-07-03 14:49 ` [PATCH 1/2] fs: no need to check source Christian Brauner
2023-07-03 14:49 ` [PATCH 2/2] fs: don't assume arguments are non-NULL Christian Brauner
2023-07-03 16:23 ` [PATCH 0/2] fs: rename follow-up fixes Jan Kara
2023-07-04 8:14 ` Christian Brauner [this message]
2023-07-04 8:22 ` Christian Brauner
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=20230704-dankbar-zweihundert-c8b44d516e2a@brauner \
--to=brauner@kernel.org \
--cc=amir73il@gmail.com \
--cc=dan.carpenter@linaro.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=miklos@szeredi.hu \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).