public inbox for linux-cifs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Steve French <smfrench@gmail.com>
Cc: Namjae Jeon <namjae.jeon@samsung.com>,
	Aur??lien Aptel <aurelien.aptel@gmail.com>,
	Christoph Hellwig <hch@infradead.org>,
	COMMON INTERNET FILE SYSTEM SERVER 
	<linux-cifsd-devel@lists.sourceforge.net>,
	CIFS <linux-cifs@vger.kernel.org>,
	ronnie sahlberg <ronniesahlberg@gmail.com>
Subject: Re: ksmbd mailing list
Date: Wed, 23 Jun 2021 05:52:40 +0100	[thread overview]
Message-ID: <YNK+GKA0aXoxhgdF@infradead.org> (raw)
In-Reply-To: <CAH2r5msB8Y8qn+DFV=3g=K791p1ssFJh=+yNOC4bG8iW3K07tw@mail.gmail.com>

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:

  parent reply	other threads:[~2021-06-23  4:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20210622061228epcas1p247d557ef24a971eaf395edd6174bed5e@epcas1p2.samsung.com>
2021-06-22  6:12 ` ksmbd mailing list 'Christoph Hellwig'
2021-06-22  6:58   ` Namjae Jeon
2021-06-22 10:37     ` Aurélien Aptel
2021-06-23  2:41       ` Namjae Jeon
2021-06-23  2:52         ` Steve French
2021-06-23  4:01           ` Namjae Jeon
2021-06-23  4:52           ` Christoph Hellwig [this message]
2021-06-23  5:04             ` 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=YNK+GKA0aXoxhgdF@infradead.org \
    --to=hch@infradead.org \
    --cc=aurelien.aptel@gmail.com \
    --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