All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Bart Van Assche <bart.vanassche@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	linux-scsi@vger.kernel.org, Vladislav Bolkhovitin <vst@vlnb.net>,
	scst-devel@lists.sourceforge.net
Subject: Re: [PATCH 2.6.25.1] Add scsi_execute_async_fifo()
Date: Fri, 2 May 2008 10:16:29 -0600	[thread overview]
Message-ID: <20080502161629.GF14976@parisc-linux.org> (raw)
In-Reply-To: <e2e108260805020906w7f5e92bev46b8d0f96aa7b4d6@mail.gmail.com>

On Fri, May 02, 2008 at 06:06:59PM +0200, Bart Van Assche wrote:
> James Bottomley clearly expressed in that thread that he doesn't want
> to maintain two SCSI target frameworks. So what I propose is that SCST
> is included in the mainline and afterwards that it is evaluated
> whether or not it is desirable to keep other target code in the
> mainline kernel.

That's not the way it works, sorry.

The way to get SCST in is to work with the people who care about target
frameworks (which doesn't include me, fwiw).  You come to a consensus
about the way to proceed.  Normally this will be a gradual migration of
the good bits from SCST into the kernel.  In *exceptional* circumstances,
we've replaced one piece of infrastructure with another (eg wireless
midlayers), but those are by no means the preferred ways to go.

Let me just re-emphasise this bit.  You HAVE to work with the existing
people.  If you can't come to a common understanding, your code won't
get in.  Even if it's better.

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

  reply	other threads:[~2008-05-02 16:16 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02 14:38 [PATCH 2.6.25.1] Add scsi_execute_async_fifo() Bart Van Assche
2008-05-02 15:33 ` Christoph Hellwig
2008-05-02 15:53   ` Bart Van Assche
2008-05-02 15:55     ` Christoph Hellwig
2008-05-02 16:06       ` Bart Van Assche
2008-05-02 16:16         ` Matthew Wilcox [this message]
2008-05-02 16:23           ` Bart Van Assche
2008-05-02 16:30             ` James Bottomley
2008-05-02 16:43               ` Bart Van Assche
2008-05-02 16:49             ` Matthew Wilcox
2008-05-02 16:57               ` Bart Van Assche
2008-05-02 17:02                 ` Matthew Wilcox
2008-05-02 18:21                   ` Vladislav Bolkhovitin
2008-05-02 16:18         ` James Bottomley
2008-05-02 16:39           ` Bart Van Assche
2008-05-02 18:09           ` Vladislav Bolkhovitin
2008-05-02 18:17           ` SCSI target subsystem Vladislav Bolkhovitin
2008-05-03  9:41             ` Bart Van Assche
2008-05-03  9:53               ` Matthew Wilcox
2008-05-03 10:39                 ` Bart Van Assche
2008-05-03 13:28                   ` Matthew Wilcox
2008-05-03 14:48                     ` Bart Van Assche
2008-05-04 15:53                   ` Bart Van Assche
2008-05-04 11:35                 ` Vladislav Bolkhovitin
2008-05-04 15:23             ` Vladislav Bolkhovitin
2008-05-04 11:48       ` [PATCH 2.6.25.1] Add scsi_execute_async_fifo() Vladislav Bolkhovitin
2008-05-04 17:53         ` Boaz Harrosh
2008-05-13 16:48           ` Vladislav Bolkhovitin
2008-05-13 17:35             ` Boaz Harrosh
2008-05-14 15:58               ` [Scst-devel] " Vladislav Bolkhovitin
2008-05-14 16:38                 ` Boaz Harrosh
2008-05-14 16:49                   ` Vladislav Bolkhovitin
2008-05-04 15:30       ` Bart Van Assche
2008-05-08 15:02         ` Bart Van Assche
2008-05-08 15:54           ` [Scst-devel] " Arne Redlich
2008-05-13 16:47             ` Vladislav Bolkhovitin

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=20080502161629.GF14976@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=bart.vanassche@gmail.com \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=scst-devel@lists.sourceforge.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.