public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Vladislav Bolkhovitin <vst@vlnb.net>
Cc: "Nicholas A. Bellinger" <nab@linux-iscsi.org>,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Spamming linux-kernel and linux-scsi by out-of-tree patches	(LIO)
Date: Mon, 26 Jan 2009 16:37:31 +0000	[thread overview]
Message-ID: <1232987851.3248.29.camel@localhost.localdomain> (raw)
In-Reply-To: <497DDFF8.8070707@vlnb.net>

On Mon, 2009-01-26 at 19:08 +0300, Vladislav Bolkhovitin wrote:
> James Bottomley, on 01/26/2009 06:37 PM wrote:
> > On Mon, 2009-01-26 at 16:17 +0300, Vladislav Bolkhovitin wrote:
> >> Nicholas,
> >>
> >> Could you stop spamming linux-kernel and linux-scsi mailing lists by 
> >> patches for your out-of-tree LIO project, please?
> >>
> >> Those mailing lists are intended for patches for in-kernel components 
> >> only, not for all out-of-tree projects, finding their ways into the 
> >> mainline. I don't see any reason why your project should be an 
> >> exception. Think, what a mess the kernel mailing lists would get, if all 
> >> out-of-tree projects started sending their patches to them?
> > 
> > Actually, out of tree projects trying to make their way upstream are
> > welcome to use the various linux- mailing lists to solicit feedback and
> > review.  This method was, for instance, how FCoE made it in.
> 
> Hmm, I might be wrong, but what I've seen that FCoE only at the 
> beginning used linux-scsi for its intermediate patches, then such 
> patches quickly went into FCoE internal development mailing list only. 
> Then only resulting patches intended for wide review and mainline 
> inclusion were sent to linux-scsi. This is how I thought it's usually 
> considered should be done and how all the projects I've seen so far did.

The only piece I think they didn't bother with was the target, mainly
because the only wanted the initator upstream.  But the principle is
still the same: projects trying to make their way upstream are welcome
to send patches.

> I wouldn't object if Nicholas does the same and send in linux-scsi and 
> linux-kernel a complete patchset, which we will review and discuss. But 
> he sends *intermediate* patches and this looks for me like a violation 
> of fundamental rules/intention of Linux kernel mailing lists, hence I 
> complain.

FCoE did the same thing.  Incremental patches are useful in showing
motion towards coding standards and kernel norms ... at least they gave
me the warm feeling that FCoE was heading in the right direction.

As long as the full code is in a repository somewhere anyone whose
curiosity is piqued by the patches can go and look there as well.

> So, should I understand your words that you agree if I also start 
> sending intermediate patches for SCST to linux-scsi/linux-kernel?

Certainly.

James



      parent reply	other threads:[~2009-01-26 16:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-26 13:17 Spamming linux-kernel and linux-scsi by out-of-tree patches (LIO) Vladislav Bolkhovitin
2009-01-26 15:37 ` James Bottomley
2009-01-26 16:08   ` Vladislav Bolkhovitin
2009-01-26 16:19     ` Arjan van de Ven
2009-01-26 16:44       ` Vladislav Bolkhovitin
2009-01-26 17:15       ` Nicholas A. Bellinger
2009-01-26 16:37     ` James Bottomley [this message]

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=1232987851.3248.29.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nab@linux-iscsi.org \
    --cc=vst@vlnb.net \
    /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