From: Roland Dreier <rdreier@cisco.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Divy Le Ray <divy@chelsio.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
swise@opengridcomputing.com
Subject: Re: [PATCH 1/10] cxgb3 - main header files
Date: Tue, 09 Jan 2007 09:09:21 -0800 [thread overview]
Message-ID: <ada4pr0ceke.fsf@cisco.com> (raw)
In-Reply-To: <45A3C5D5.6030105@garzik.org> (Jeff Garzik's message of "Tue, 09 Jan 2007 11:41:57 -0500")
> The time for adding new stuff to 2.6.20 is /long/ past. We stop
> adding things like new drivers when Linus releases 2.6.X-rc1.
Well, in the past I think new drivers have been added after the merge
window, given that there's no chance of regressions (old kernel == no
support for device X, so even if the new driver is buggy it's no worse
than the old kernel). (eg a quick git scan shows commit 0f64478c
added a USB driver between 2.6.19-rc2 and 2.6.19-rc3, and I'm sure you
can find lots of other examples)
Anyway, you answered my question. I wasn't pushing to include the
driver now, I just wanted to know what you were planning to do.
Thanks.
- R.
next prev parent reply other threads:[~2007-01-09 17:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 12:41 [PATCH 1/10] cxgb3 - main header files Divy Le Ray
2006-12-26 20:57 ` Jeff Garzik
2006-12-27 8:52 ` Divy Le Ray
2006-12-27 9:03 ` Arjan van de Ven
2007-01-09 10:19 ` Divy Le Ray
2007-01-09 10:28 ` Jeff Garzik
2007-01-09 13:38 ` Steve Wise
2007-01-09 13:57 ` Michael S. Tsirkin
2007-01-09 14:46 ` Steve Wise
2007-01-09 19:39 ` [openib-general] " Steve Wise
2007-01-09 18:29 ` Caitlin Bestler
2007-01-09 16:28 ` Roland Dreier
2007-01-09 16:41 ` Jeff Garzik
2007-01-09 17:09 ` Roland Dreier [this message]
2007-01-19 3:05 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2006-12-22 7:20 Divy Le Ray
2006-12-14 5:41 Divy Le Ray
2006-12-08 3:26 Divy Le Ray
2006-12-04 19:44 Divy Le Ray
2006-11-17 20:23 Divy Le Ray <divy@chelsio.com>
2006-11-17 20:49 ` Stephen Hemminger
2006-11-17 21:48 ` Roland Dreier
2006-11-18 17:25 ` Jan Engelhardt
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=ada4pr0ceke.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=divy@chelsio.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=swise@opengridcomputing.com \
/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;
as well as URLs for NNTP newsgroup(s).