From: Christoph Hellwig <hch@infradead.org>
To: Leif Sahlberg <lsahlber@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Namjae Jeon <namjae.jeon@samsung.com>,
linux-cifsd-devel@lists.sourceforge.net,
linux-cifs@vger.kernel.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 14/15] ksmbd: use ksmbd name instead of cifsd
Date: Tue, 22 Jun 2021 08:41:31 +0100 [thread overview]
Message-ID: <YNGUKx0oLgeVzYmv@infradead.org> (raw)
In-Reply-To: <CAGvGhF43zhqkLn0GBjdm28cT_wufJr0CJ4LGZOVV=SFpOr9YyA@mail.gmail.com>
On Tue, Jun 22, 2021 at 05:33:50PM +1000, Leif Sahlberg wrote:
> > Understood.
> In that case, what are your thoughts about renaming the current client
> fs/cifs tree to fs/smb ?
If it was newly added I'd be all in favor. Renaming an existing
codebase is rather painful, though. So I'd rather live with the
historic misnaming (and think of the historic smbfs predating the
current cifs driver :))
prev parent reply other threads:[~2021-06-22 7:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210618022645.27307-1-namjae.jeon@samsung.com>
[not found] ` <CGME20210618023614epcas1p4f33df1322709076c65a63f5013f9c2cc@epcas1p4.samsung.com>
[not found] ` <20210618022645.27307-14-namjae.jeon@samsung.com>
[not found] ` <YNBKb2UJQ8D4JhcO@infradead.org>
[not found] ` <009301d76677$8b52a6b0$a1f7f410$@samsung.com>
2021-06-22 6:03 ` [PATCH 14/15] ksmbd: use ksmbd name instead of cifsd 'Christoph Hellwig'
[not found] ` <CAGvGhF43zhqkLn0GBjdm28cT_wufJr0CJ4LGZOVV=SFpOr9YyA@mail.gmail.com>
2021-06-22 7:41 ` 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=YNGUKx0oLgeVzYmv@infradead.org \
--to=hch@infradead.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-cifsd-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsahlber@redhat.com \
--cc=namjae.jeon@samsung.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).