From: Christoph Hellwig <hch@infradead.org>
To: Chao Yu <yuchao0@huawei.com>
Cc: Christoph Hellwig <hch@infradead.org>,
jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH] f2fs: fix to recover inode's uid/gid during POR
Date: Thu, 20 Sep 2018 23:40:38 -0700 [thread overview]
Message-ID: <20180921064038.GA21481@infradead.org> (raw)
In-Reply-To: <f2479038-3e4e-63e3-083e-d125b4a4d919@huawei.com>
On Fri, Sep 21, 2018 at 02:20:49PM +0800, Chao Yu wrote:
> No problem, I just plan to.
>
> Out of curiosity, are you filter some key words like 'recover' in your
> email client to find this so quickly?
No, I just do a quick glanceof lkml every morning, and this just caught
my eye.
prev parent reply other threads:[~2018-09-21 6:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 9:41 [PATCH] f2fs: fix to recover inode's uid/gid during POR Chao Yu
2018-09-20 21:41 ` Jaegeuk Kim
2018-09-21 6:06 ` Christoph Hellwig
2018-09-21 6:20 ` Chao Yu
2018-09-21 6:40 ` Christoph Hellwig [this message]
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=20180921064038.GA21481@infradead.org \
--to=hch@infradead.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=yuchao0@huawei.com \
/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).