From: Steve French <smfrench@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
Namjae Jeon <namjae.jeon@samsung.com>,
CIFS <linux-cifs@vger.kernel.org>
Subject: Re: [bug report] cifsd: introduce SMB3 kernel server
Date: Fri, 19 Mar 2021 10:27:30 -0500 [thread overview]
Message-ID: <CAH2r5mtpvzvFxebwbbpQ1d2hU0Zz0k67+=M-k+YPeqKneQZ6Lw@mail.gmail.com> (raw)
In-Reply-To: <20210319152110.GA1100251@infradead.org>
On Fri, Mar 19, 2021 at 10:21 AM Christoph Hellwig <hch@infradead.org> wrote:
>
> Code that goes into linux-next needs to be posted to the relevant
> lists, which in this case includes linux-fsdevel and linux-kernel. No
> backstory of conference and internal trees replaces that in any way.
Yes - agree.
When I last talked with Namjae (and looks like he asked others for
opinions as well
how to restructure the patch series to be easier to review on
linux-fsdevel), the
plan was to send the patches to fsdevel as the smaller set (same as just
went in linux-next) ASAP, but he just finished an important piece of the
description (the updated protocol feature implementation summary) last
night which
he asked me (and probably others) to review before sending it out.
--
Thanks,
Steve
next prev parent reply other threads:[~2021-03-19 15:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 13:12 [bug report] cifsd: introduce SMB3 kernel server Dan Carpenter
[not found] ` <CAH2r5msOBAho=1W-eY0paj+4P1J+tuw-vFaRGg8oY50dXu6MHQ@mail.gmail.com>
2021-03-19 8:11 ` Dan Carpenter
2021-03-19 13:12 ` Christoph Hellwig
2021-03-19 15:07 ` Steve French
2021-03-19 15:21 ` Christoph Hellwig
2021-03-19 15:27 ` Steve French [this message]
2021-04-06 8:37 ` L. A. Walsh
2021-04-06 10:14 ` Aurélien Aptel
2021-04-06 22:55 ` cifsd: introduce <SMB2n3> " L. A. Walsh
2021-04-06 23:32 ` Namjae Jeon
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='CAH2r5mtpvzvFxebwbbpQ1d2hU0Zz0k67+=M-k+YPeqKneQZ6Lw@mail.gmail.com' \
--to=smfrench@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=hch@infradead.org \
--cc=linux-cifs@vger.kernel.org \
--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).