From: Jeff Garzik <jeff@garzik.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PATCH] scsi fixes for 2.6.25-rc2
Date: Sat, 23 Feb 2008 15:25:24 -0500 [thread overview]
Message-ID: <47C08134.2030205@garzik.org> (raw)
In-Reply-To: <1203779614.3139.4.camel@localhost.localdomain>
James Bottomley wrote:
> This is the latest crop of bug fixes plus one new driver: mvsas. We're
[...]
> Jeff Garzik (1):
> mvsas: Add Marvell 6440 SAS/SATA driver
[...]
> Ke Wei (1):
> mvsas: convert from rough draft to working driver
I know I am probably shooting myself in the foot here, since I am the
original author of mvsas, but...
Should we be adding new drivers during -rc?
On one hand, it's clear the addition does not break anything, and adds
value for users.
On the other hand, it's clearly not a bug fix, and -rc could easily get
bloated with new drivers that didn't make the merge window.
On the net driver side of things, I have a few new net drivers that I
have queued for 2.6.26, because they did not make the merge window.
This is inconsistent with your apparently policy.
I would just prefer to have a clear and consistent policy here,
regarding new drivers during -rc.
Thanks,
Jeff
next prev parent reply other threads:[~2008-02-23 20:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-23 15:13 [GIT PATCH] scsi fixes for 2.6.25-rc2 James Bottomley
2008-02-23 20:25 ` Jeff Garzik [this message]
2008-02-23 20:27 ` Jeff Garzik
2008-02-23 20:31 ` Linus Torvalds
2008-02-23 20:44 ` Andrew Morton
2008-02-23 23:53 ` Jeff Garzik
2008-02-23 20:56 ` James Bottomley
2008-02-23 23:01 ` Olof Johansson
2008-02-23 23:31 ` Jeff Garzik
2008-02-24 0:09 ` James Bottomley
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=47C08134.2030205@garzik.org \
--to=jeff@garzik.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@linux-foundation.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