From: Christoph Hellwig <hch@infradead.org>
To: Namjae Jeon <namjae.jeon@samsung.com>
Cc: linux-cifs@vger.kernel.org,
linux-cifsd-devel@lists.sourceforge.net,
Steve French <smfrench@gmail.com>,
Ronnie Sahlberg <ronniesahlberg@gmail.com>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH 1/2] ksmbd: move fs/cifsd to fs/ksmbd
Date: Thu, 24 Jun 2021 06:25:45 +0100 [thread overview]
Message-ID: <YNQXWd/Bwdmpd6Ih@infradead.org> (raw)
In-Reply-To: <20210624005211.26886-1-namjae.jeon@samsung.com>
On Thu, Jun 24, 2021 at 09:52:10AM +0900, Namjae Jeon wrote:
> Move fs/cifsd to fs/ksmbd and rename the remaining cifsd name to ksmbd.
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
prev parent reply other threads:[~2021-06-24 5:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210624010230epcas1p27cee803b261296294a069e8169a03c4a@epcas1p2.samsung.com>
2021-06-24 0:52 ` [PATCH 1/2] ksmbd: move fs/cifsd to fs/ksmbd Namjae Jeon
[not found] ` <CGME20210624010231epcas1p22d8b6576f5966f45cbf9bf99331dec53@epcas1p2.samsung.com>
2021-06-24 0:52 ` [PATCH 2/2] MAINTAINERS: rename cifsd to ksmbd Namjae Jeon
2021-06-24 5:27 ` Christoph Hellwig
2021-06-24 5:25 ` 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=YNQXWd/Bwdmpd6Ih@infradead.org \
--to=hch@infradead.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-cifsd-devel@lists.sourceforge.net \
--cc=namjae.jeon@samsung.com \
--cc=ronniesahlberg@gmail.com \
--cc=smfrench@gmail.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).