From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Randy Dunlap <rdunlap@infradead.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>, Chao Yu <yuchao0@huawei.com>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH] f2fs: Documentation edits/fixes
Date: Thu, 3 Sep 2020 10:40:07 -0700 [thread overview]
Message-ID: <20200903174007.GA3619770@google.com> (raw)
In-Reply-To: <20200903103027.4c8d0b07@lwn.net>
On 09/03, Jonathan Corbet wrote:
> On Wed, 2 Sep 2020 17:08:31 -0700
> Randy Dunlap <rdunlap@infradead.org> wrote:
>
> > From: Randy Dunlap <rdunlap@infradead.org>
> >
> > Correct grammar and spelling.
> >
> > Drop duplicate section for resize.f2fs.
> >
> > Change one occurrence of F2fs to F2FS for consistency.
> >
> > Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> > Cc: Jaegeuk Kim <jaegeuk@kernel.org>
> > Cc: Chao Yu <yuchao0@huawei.com>
> > Cc: linux-f2fs-devel@lists.sourceforge.net
> > ---
> > Documentation/filesystems/f2fs.rst | 53 +++++++++++----------------
> > 1 file changed, 23 insertions(+), 30 deletions(-)
>
> So this, I guess, needs to go through the f2fs tree since it doesn't apply
> to docs-next currently.
Yup, I applied in f2fs tree.
Thanks,
>
> Thanks,
>
> jon
WARNING: multiple messages have this Message-ID (diff)
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Randy Dunlap <rdunlap@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-f2fs-devel@lists.sourceforge.net,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [f2fs-dev] [PATCH] f2fs: Documentation edits/fixes
Date: Thu, 3 Sep 2020 10:40:07 -0700 [thread overview]
Message-ID: <20200903174007.GA3619770@google.com> (raw)
In-Reply-To: <20200903103027.4c8d0b07@lwn.net>
On 09/03, Jonathan Corbet wrote:
> On Wed, 2 Sep 2020 17:08:31 -0700
> Randy Dunlap <rdunlap@infradead.org> wrote:
>
> > From: Randy Dunlap <rdunlap@infradead.org>
> >
> > Correct grammar and spelling.
> >
> > Drop duplicate section for resize.f2fs.
> >
> > Change one occurrence of F2fs to F2FS for consistency.
> >
> > Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> > Cc: Jaegeuk Kim <jaegeuk@kernel.org>
> > Cc: Chao Yu <yuchao0@huawei.com>
> > Cc: linux-f2fs-devel@lists.sourceforge.net
> > ---
> > Documentation/filesystems/f2fs.rst | 53 +++++++++++----------------
> > 1 file changed, 23 insertions(+), 30 deletions(-)
>
> So this, I guess, needs to go through the f2fs tree since it doesn't apply
> to docs-next currently.
Yup, I applied in f2fs tree.
Thanks,
>
> Thanks,
>
> jon
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2020-09-03 17:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 0:08 [PATCH] f2fs: Documentation edits/fixes Randy Dunlap
2020-09-03 0:08 ` [f2fs-dev] " Randy Dunlap
2020-09-03 1:20 ` Chao Yu
2020-09-03 1:20 ` [f2fs-dev] " Chao Yu
2020-09-03 16:30 ` Jonathan Corbet
2020-09-03 16:30 ` [f2fs-dev] " Jonathan Corbet
2020-09-03 17:40 ` Jaegeuk Kim [this message]
2020-09-03 17:40 ` Jaegeuk Kim
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=20200903174007.GA3619770@google.com \
--to=jaegeuk@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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 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.