mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oleg Drokin <green@linuxhacker.ru>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH 09/10] lustre: Add MAINTAINERS entry
Date: Sun, 17 Aug 2014 12:47:57 -0400	[thread overview]
Message-ID: <980AF87D-E1F4-4C0E-AFF3-DB170DB98ADA@linuxhacker.ru> (raw)
In-Reply-To: <20140817163739.GA15982@kroah.com>


On Aug 17, 2014, at 12:37 PM, Greg Kroah-Hartman wrote:

> On Fri, Aug 15, 2014 at 12:48:14PM -0400, Oleg Drokin wrote:
>> Just add the entry with some info.
>> 
>> Signed-off-by: Oleg Drokin <green@linuxhacker.ru>
>> ---
>> MAINTAINERS | 8 ++++++++
>> 1 file changed, 8 insertions(+)
>> 
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 7e2eb4c..369183b 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -8646,6 +8646,14 @@ W:	http://www.lirc.org/
>> S:	Odd Fixes
>> F:	drivers/staging/media/lirc/
>> 
>> +STAGING - LUSTRE PARALLEL FILESYSTEM
>> +M:	Oleg Drokin <oleg.drokin@intel.com>
>> +M:	Andreas Dilger <andreas.dilger@intel.com>
>> +L:	HPDD-discuss@lists.01.org (moderated for non-subscribers)
> 
> I _really_ hate moderated mailing lists for kernel development stuff.
> Why not just use the driverdev mailing list instead?

I guess this could be done if we really need to, but ...

> I note that you didn't even cc: this patch series to that list...

The instructions in the beginning of the file say:
"L: Mailing list that is relevant to this area"
This is the mailing list that is relevant to the area, but we don't really send patches in there,
and because it's premoderated it's not really convenient anyway as you rightly notice.
People can ask other questions they might have bout their problems there, though, and there's
a higher chance that somebody familiar with lustre will read and answer them.

the 'M:' is the send patches to according to the instructions?

The patches are CCed to linux-kernel by most everybody anyway, so do we really need to
spell this out explicitly with an 'L:' line or in some other way?

  reply	other threads:[~2014-08-17 16:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-15 16:48 [PATCH 00/10] Catchup lustre fixes Oleg Drokin
2014-08-15 16:48 ` [PATCH 01/10] staging/lustre/llite: check for integer overflow in hsm user request Oleg Drokin
2014-08-15 16:48 ` [PATCH 02/10] staging/lustre/mdc: cleanup intent if mdc_finish_enqueue() fails Oleg Drokin
2014-08-15 16:48 ` [PATCH 03/10] staging/lustre/llite: Make sure ft_flags is valid Oleg Drokin
2014-08-15 16:48 ` [PATCH 04/10] staging/lustre/ldlm: drop redundant ibits lock interoperability check Oleg Drokin
2014-08-15 16:48 ` [PATCH 05/10] staging/lustre/clio: reorder initialization in cl_req_alloc() Oleg Drokin
2014-08-15 16:48 ` [PATCH 06/10] staging/lustre/llite: hold inode mutex around ll_setattr_raw() Oleg Drokin
2014-08-15 16:48 ` [PATCH 07/10] staging/lustre/llite: optimize ll_fid2path() Oleg Drokin
2014-08-15 16:48 ` [PATCH 08/10] staging/lustre/llite: Fix integer overflow in ll_fid2path Oleg Drokin
2014-08-15 16:48 ` [PATCH 09/10] lustre: Add MAINTAINERS entry Oleg Drokin
2014-08-17 16:37   ` Greg Kroah-Hartman
2014-08-17 16:47     ` Oleg Drokin [this message]
2014-08-18 14:21       ` Dan Carpenter
2014-08-30 18:51       ` Greg Kroah-Hartman
2014-08-15 16:48 ` [PATCH 10/10] lustre: Add some basic documentation Oleg Drokin
2014-08-17 16:37   ` Greg Kroah-Hartman
2014-08-17 16:49     ` Oleg Drokin
2014-08-17 16:53       ` Greg Kroah-Hartman

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=980AF87D-E1F4-4C0E-AFF3-DB170DB98ADA@linuxhacker.ru \
    --to=green@linuxhacker.ru \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®