linux-cifs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: 'Christoph Hellwig' <hch@infradead.org>
To: Namjae Jeon <namjae.jeon@samsung.com>
Cc: 'Christoph Hellwig' <hch@infradead.org>,
	linux-cifsd-devel@lists.sourceforge.net,
	linux-cifs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 14/15] ksmbd: use ksmbd name instead of cifsd
Date: Tue, 22 Jun 2021 07:03:16 +0100	[thread overview]
Message-ID: <YNF9JB7PrSOpfWIP@infradead.org> (raw)
In-Reply-To: <009301d76677$8b52a6b0$a1f7f410$@samsung.com>

On Mon, Jun 21, 2021 at 05:29:25PM +0900, Namjae Jeon wrote:
> > On Fri, Jun 18, 2021 at 11:26:44AM +0900, Namjae Jeon wrote:
> > > Use ksmbd name instead of cifsd.
> > 
> > I think you probably want to move fs/cifsd to fs/ksmbd/ as well then.
> We had a lot of discussion about this and decided to leave the directory name as cifsd.
> Please see:
>    https://lkml.org/lkml/2021/4/6/1296

I can't really agree with that argument.  If we have a module that is
called ksmbd fs/ksmbd/ is the right place for it.  And having a
smb_common module used by ksmbd and cifs should not be too bad for those
who know just a little about the smb/cifs history.

       reply	other threads:[~2021-06-22  6:04 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         ` 'Christoph Hellwig' [this message]
     [not found]           ` <CAGvGhF43zhqkLn0GBjdm28cT_wufJr0CJ4LGZOVV=SFpOr9YyA@mail.gmail.com>
2021-06-22  7:41             ` Christoph Hellwig

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=YNF9JB7PrSOpfWIP@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=namjae.jeon@samsung.com \
    --subject='Re: [PATCH 14/15] ksmbd: use ksmbd name instead of cifsd' \
    /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

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).