From: Jeff Garzik <jeff@garzik.org>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: netdev@vger.kernel.org, Greg KH <greg@kroah.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 00/17] sky2 update for 2.6.22
Date: Wed, 09 May 2007 19:27:17 -0400 [thread overview]
Message-ID: <464258D5.5040402@garzik.org> (raw)
In-Reply-To: <20070509074811.23ba0bb9@freekitty>
Stephen Hemminger wrote:
> On Wed, 09 May 2007 00:16:48 -0400
> Jeff Garzik <jeff@garzik.org> wrote:
>
>> Stephen Hemminger wrote:
>>> Patches are against netdev-2.6 upstream code branch.
>>>
>>> This includes a several bug fixes, and code cleanup to use standard
>>> functions. There are a couple of PCI changes. One bug fix, and moving
>>> common code in PCI base.
>> The standard development process is:
>>
>> * new code gets pushed to me during 2.6.X-rc
>> * that code is auto-propagated to akpm's -mm tree for
>> additional exposure
>> * merge window opens
>> * I push upstream
>>
>> That ensures code gets at least /some/ additional review, testing,
>> "settling" time.
>
> Sorry for the late merge, but between the closing of OSDL office and
> the fixing of critical bugs the other stuff got pushed into the "next release"
> bin and wasn't really ready until now.
>
>> This is a late date to be expecting stuff to be pushed straight into 2.6.22.
>
> Then hold it for 2.6.23.
You sure you don't want to split off the bug fixes, and submit those for
2.6.22?
An oops fix is certainly 2.6.22 material...
>> Additionally, the rule for creating patches is: diff against latest
>> vanilla linux-2.6.git tree, unless dependencies exist in netdev. After
>> the merge window opens, #upstream is often empty or even a bit behind
>> upstream, since Linus pulls that.
>
> One patch wouldn't have applied unless the recent patch that you
> accepted was included.
OK, I stand corrected on this issue, then. It sounds like you diff'd
correctly.
Jeff
next prev parent reply other threads:[~2007-05-09 23:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 3:49 [PATCH 00/17] sky2 update for 2.6.22 Stephen Hemminger
2007-05-09 3:49 ` [PATCH 01/17] sky2: fix oops on shutdown Stephen Hemminger
2007-05-09 3:49 ` [PATCH 02/17] sky2: dont restrict config space access Stephen Hemminger
2007-05-09 3:49 ` [PATCH 03/17] sky2: keep track of receive alloc failures Stephen Hemminger
2007-05-09 3:49 ` [PATCH 04/17] sky2: remove dual port workaround Stephen Hemminger
2007-05-09 3:49 ` [PATCH 05/17] pci: advanced error reporting stub return values Stephen Hemminger
2007-05-10 15:48 ` Stephen Hemminger
2007-05-09 3:49 ` [PATCH 06/17] sky2: advanced error reporting Stephen Hemminger
2007-05-09 17:05 ` Linas Vepstas
2007-05-09 22:35 ` Stephen Hemminger
2007-05-09 3:49 ` [PATCH 07/17] sky2: use pci_config access functions Stephen Hemminger
2007-05-09 3:49 ` [PATCH 08/17] sky2: MIB counter overflow handling Stephen Hemminger
2007-05-09 3:49 ` [PATCH 09/17] sky2: memory barriers change Stephen Hemminger
2007-05-09 3:49 ` [PATCH 10/17] sky2: add prefetch for next skb on receive Stephen Hemminger
2007-05-09 3:50 ` [PATCH 11/17] sky2: use MII defines Stephen Hemminger
2007-05-09 3:50 ` [PATCH 12/17] sky2: chip id enum Stephen Hemminger
2007-05-09 3:50 ` [PATCH 13/17] sky2: whitespace cleanups Stephen Hemminger
2007-05-09 3:50 ` [PATCH 14/17] pci_wake_enabled function Stephen Hemminger
2007-05-09 3:50 ` [PATCH 15/17] sky2: only disable 88e8056 on some boards Stephen Hemminger
2007-05-09 3:50 ` [PATCH 16/17] sky2: make sure high DMA bits set Stephen Hemminger
2007-05-09 3:50 ` [PATCH 17/17] sky2: version 1.15 Stephen Hemminger
2007-05-09 4:16 ` [PATCH 00/17] sky2 update for 2.6.22 Jeff Garzik
2007-05-09 14:48 ` Stephen Hemminger
2007-05-09 23:27 ` Jeff Garzik [this message]
2007-05-10 5:08 ` Stephen Hemminger
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=464258D5.5040402@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@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;
as well as URLs for NNTP newsgroup(s).