public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: John Stoffel <john@stoffel.org>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
	Jens Axboe <Jens.Axboe@oracle.com>
Subject: Re: SCSI git trees
Date: Mon, 03 Aug 2009 18:57:05 +0000	[thread overview]
Message-ID: <1249325826.3943.207.camel@mulgrave.site> (raw)
In-Reply-To: <19063.9181.620137.814464@stoffel.org>

On Mon, 2009-08-03 at 13:52 -0400, John Stoffel wrote:
> >>>>> "James" == James Bottomley <James.Bottomley@HansenPartnership.com> writes:
> 
> James> It seems I got unsubscribed from linux-scsi last week while I was on
> James> holiday and I've likely missed a slew of patches, it seems like an
> James> appropriate time to remind everyone how the SCSI trees work.
> 
> James> ---
> 
> James> There are two git based scsi trees:
> 
> James> http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-misc-2.6.git
> 
> James> called the scsi-misc tree for patches being collected for the
> James> next merge window.  And
> 
> I don't see my patch to block/Kconfig to make BLK_DEV_BSG be enabled
> by default.  Is this going to be pushed for 2.6.32-rc1 when the merge
> window opens up?  
> 
> I've attached the patch, just to make sure.  Let me know if I should
> send it in properly.
> 
> Thanks!
> John
> 
> 
> Make Block Layer SG support v4 the default, since recent udev versions
> depend on this to access serial numbers and other low level info
> properly.
> 
> This should be backported to older kernels as well, since most distros
> have
> enabled this for a long time.
> 
> Signed-off-by: John Stoffel <john@stoffel.org>
> ---
>  block/Kconfig |   11 +++++++----
>  1 files changed, 7 insertions(+), 4 deletions(-)
> 
> diff --git a/block/Kconfig b/block/Kconfig
> index e7d1278..55bbefc 100644
> --- a/block/Kconfig
> +++ b/block/Kconfig

Actually, this one isn't really SCSI; it's block (Jens cc'd).  It's Jens
call on the backport, but my feeling is that removing a feature from
experimental is really an enhancement not a bug fix, so it's not really
eligible under the backport rules.

James



  parent reply	other threads:[~2009-08-03 18:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-29 17:07 SCSI git trees James Bottomley
2009-08-03 17:52 ` John Stoffel
2009-08-03 18:09   ` Randy Dunlap
2009-08-03 19:00     ` James Bottomley
2009-08-03 18:57   ` James Bottomley [this message]
2009-08-03 19:13     ` John Stoffel
2009-08-03 20:27       ` Jens Axboe
2009-08-03 21:00         ` John Stoffel
2009-08-03 21:04           ` Jens Axboe
2009-08-04 16:37             ` John Stoffel
2009-08-04 20:15               ` Jens Axboe
2009-08-04 20:27                 ` John Stoffel
2009-08-04 20:36                   ` Jens Axboe
2009-08-04 20:45                   ` 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=1249325826.3943.207.camel@mulgrave.site \
    --to=james.bottomley@hansenpartnership.com \
    --cc=Jens.Axboe@oracle.com \
    --cc=john@stoffel.org \
    --cc=linux-scsi@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