ksmbd mailing list

ksmbd mailing list

['Christoph Hellwig']

Is there a good reason to have a ksmbd-specific list instead of pooling
all the smb3 knowledge on a single list, similar to how nfs development
works?

RE: ksmbd mailing list

[Namjae Jeon]

> Is there a good reason to have a ksmbd-specific list instead of pooling all the smb3 knowledge on a
> single list, similar to how nfs development works?
There are users who subscribe only to ksmbd-specific list since ksmbd is out of tree. So we specified
both lists in MAINTAINERS. I do not object to use single list and kill the specific list after
ksmbd is merged into mainline.

Add CC: Steve, Ronnie, Aurélien.
Any opinions?

Thanks!

RE: ksmbd mailing list

[Aurélien Aptel]

"Namjae Jeon" <namjae.jeon@samsung.com> writes:
> Add CC: Steve, Ronnie, Aurélien.
> Any opinions?

I think having only one list would be nice too, but we should
ask/document to put a [cifsd] tag somewhere in the subject, which is
hard to enforce.

Case in point, it already gets confusing when people send patches for
cifs-utils: we can't always tell it's not for the kernel from the
subject which can confuse people and scripts.

Cheers,
-- 
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97  8C99 03C8 A49B 521B D5D3
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg, DE
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 247165 (AG München)

RE: ksmbd mailing list

[Namjae Jeon]

> "Namjae Jeon" <namjae.jeon@samsung.com> writes:
> > Add CC: Steve, Ronnie, Aurélien.
> > Any opinions?
> 
> I think having only one list would be nice too, but we should ask/document to put a [cifsd] tag
> somewhere in the subject, which is hard to enforce.
> 
> Case in point, it already gets confusing when people send patches for
> cifs-utils: we can't always tell it's not for the kernel from the subject which can confuse people and
> scripts.
Thanks for your opinion!
I will change to specify single list(linux-cifs@vger.kernel.org) in MAINTAINERS.

> Cheers,
> --
> Aurélien Aptel / SUSE Labs Samba Team
> GPG: 1839 CB5F 9F5B FB9B AA97  8C99 03C8 A49B 521B D5D3 SUSE Software Solutions Germany GmbH,
> Maxfeldstr. 5, 90409 Nürnberg, DE
> GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 247165 (AG München)

Re: ksmbd mailing list

[Steve French]

We should probably put a few lines in the cifsd and cifs client wiki
pages on samba.org and also in the kernel documentation directory for
each that notes that emails with patches should have a prefix that
indicates whether server or client or utils (e.g. [cifsd] or [ksmbd]
if you prefer, [cifs] for the client and [cifs-utils] for the tools)

On Tue, Jun 22, 2021 at 9:41 PM Namjae Jeon <namjae.jeon@samsung.com> wrote:
>
> > "Namjae Jeon" <namjae.jeon@samsung.com> writes:
> > > Add CC: Steve, Ronnie, Aurélien.
> > > Any opinions?
> >
> > I think having only one list would be nice too, but we should ask/document to put a [cifsd] tag
> > somewhere in the subject, which is hard to enforce.
> >
> > Case in point, it already gets confusing when people send patches for
> > cifs-utils: we can't always tell it's not for the kernel from the subject which can confuse people and
> > scripts.
> Thanks for your opinion!
> I will change to specify single list(linux-cifs@vger.kernel.org) in MAINTAINERS.
>
> > Cheers,
> > --
> > Aurélien Aptel / SUSE Labs Samba Team
> > GPG: 1839 CB5F 9F5B FB9B AA97  8C99 03C8 A49B 521B D5D3 SUSE Software Solutions Germany GmbH,
> > Maxfeldstr. 5, 90409 Nürnberg, DE
> > GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 247165 (AG München)
>
>


-- 
Thanks,

Steve

RE: ksmbd mailing list

[Namjae Jeon]

> We should probably put a few lines in the cifsd and cifs client wiki pages on samba.org and also in
> the kernel documentation directory for each that notes that emails with patches should have a prefix
> that indicates whether server or client or utils (e.g. [cifsd] or [ksmbd] if you prefer, [cifs] for
> the client and [cifs-utils] for the tools)
Okay, I will update it in wiki and kernel documentation.

Thanks!
> 
> On Tue, Jun 22, 2021 at 9:41 PM Namjae Jeon <namjae.jeon@samsung.com> wrote:
> >
> > > "Namjae Jeon" <namjae.jeon@samsung.com> writes:
> > > > Add CC: Steve, Ronnie, Aurélien.
> > > > Any opinions?
> > >
> > > I think having only one list would be nice too, but we should
> > > ask/document to put a [cifsd] tag somewhere in the subject, which is hard to enforce.
> > >
> > > Case in point, it already gets confusing when people send patches
> > > for
> > > cifs-utils: we can't always tell it's not for the kernel from the
> > > subject which can confuse people and scripts.
> > Thanks for your opinion!
> > I will change to specify single list(linux-cifs@vger.kernel.org) in MAINTAINERS.
> >
> > > Cheers,
> > > --
> > > Aurélien Aptel / SUSE Labs Samba Team
> > > GPG: 1839 CB5F 9F5B FB9B AA97  8C99 03C8 A49B 521B D5D3 SUSE
> > > Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg, DE
> > > GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 247165 (AG
> > > München)
> >
> >
> 
> 
> --
> Thanks,
> 
> Steve

Re: ksmbd mailing list

[Christoph Hellwig]

On Tue, Jun 22, 2021 at 09:52:33PM -0500, Steve French wrote:
> We should probably put a few lines in the cifsd and cifs client wiki
> pages on samba.org and also in the kernel documentation directory for
> each that notes that emails with patches should have a prefix that
> indicates whether server or client or utils (e.g. [cifsd] or [ksmbd]
> if you prefer, [cifs] for the client and [cifs-utils] for the tools)

The normal kernel patch prefixes would be:

cifs:

and

ksmbd:

RE: ksmbd mailing list

[Namjae Jeon]

> 
> On Tue, Jun 22, 2021 at 09:52:33PM -0500, Steve French wrote:
> > We should probably put a few lines in the cifsd and cifs client wiki
> > pages on samba.org and also in the kernel documentation directory for
> > each that notes that emails with patches should have a prefix that
> > indicates whether server or client or utils (e.g. [cifsd] or [ksmbd]
> > if you prefer, [cifs] for the client and [cifs-utils] for the tools)
> 
> The normal kernel patch prefixes would be:
> 
> cifs:
> 
> and
> 
> ksmbd:
Yes, Sure:)