public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: John Stoffel <john@stoffel.org>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@kernel.org
Subject: Re: [PATCH 5/5] Make SCSI SG v4 driver enabled by default and remove EXPERIMENTAL dependency, since udev depends on BSG.
Date: Tue, 14 Jul 2009 10:22:16 -0400	[thread overview]
Message-ID: <1247581336.4310.60.camel@mulgrave.site> (raw)
In-Reply-To: <4A5C923B.9090109@panasas.com>

On Tue, 2009-07-14 at 17:12 +0300, Boaz Harrosh wrote:
> On 07/14/2009 04:29 PM, James Bottomley wrote:
> > On Tue, 2009-07-14 at 09:38 +0300, Boaz Harrosh wrote:
> >> On 07/13/2009 10:43 PM, John Stoffel wrote:
> >>>>>>>> "John" == John Stoffel <john@stoffel.org> writes:
> >>> Dammit, I messed up here sending this patch.  I've just edited the
> >>> subject line and re-sent it with a bit more description.  I think this
> >>> patch is perfectly good to go into 2.6.31 right now, esp since it's
> >>> not changing code, just whether the code is turned on by default from
> >>> now on.
> >>>
> >> I would like it if you'd also CC stable@kernel.org on this patch. As this
> >> condition is already true for distros in the field.
> > 
> > The stable tree is for bug *fixes*.   Moving an option out from under
> > experimental is basically an enhancement, even if it could be argued it
> > should have been done long ago.
> > 
> 
> wouldn't you consider it a bug if a low-level plumbing like Udev is shipped
> with hard dependency on it?

Sure .. file a bug with udev ...

The point is that if you use a feature marked "Experimental, do not use"
it's not a bug in the provider if you use it.

Arguably, all this really shows is that the distros ignore EXPERIMENTAL,
so it's not really serving a useful purpose in the kernel.

> if Udev was part of Kconfig it would have a "depend" on bsg. But because
> it's a different product it can only rely on defaults?

James



  reply	other threads:[~2009-07-14 14:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-13 19:39 [PATCH 5/5] Make SCSI SG v4 driver enabled by default and remove EXPERIMENTAL dependency, since udev depends on BSG John Stoffel
2009-07-13 19:43 ` John Stoffel
2009-07-14  6:38   ` Boaz Harrosh
2009-07-14 13:16     ` John Stoffel
2009-07-14 13:29     ` James Bottomley
2009-07-14 14:12       ` Boaz Harrosh
2009-07-14 14:22         ` James Bottomley [this message]
2009-07-14 16:06       ` John Stoffel
  -- strict thread matches above, loose matches on Subject: below --
2009-07-07 15:44 John Stoffel
2009-07-07 15:37 John Stoffel

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=1247581336.4310.60.camel@mulgrave.site \
    --to=james.bottomley@hansenpartnership.com \
    --cc=bharrosh@panasas.com \
    --cc=john@stoffel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=stable@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