linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: albertl@mail.com, Tejun Heo <htejun@gmail.com>,
	linux-ide@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCHSET] libata: improve ata_bus_probe failure handling, take 2
Date: Tue, 04 Apr 2006 09:11:57 -0400	[thread overview]
Message-ID: <4432709D.2080708@pobox.com> (raw)
In-Reply-To: <87f94c370604040602i7b9a5bbfu6c9285d77c5f75ed@mail.gmail.com>

Greg Freemyer wrote:
> On 4/3/06, Jeff Garzik <jgarzik@pobox.com> wrote:
>> Greg Freemyer wrote:
>>> On 4/3/06, Jeff Garzik <jgarzik@pobox.com> wrote:
>>>
>>>> For the record, I do consider irq-pio upstream ready.  It still needs to
>>>> wait for Tejun's EH work to make it upstream, to give upstream people
>>>> the test sets of
>>>>
>>>>         - prep EH (2.6.17-rc1)
>>>>         - EH
>>>>         - NCQ
>>>>         - irq-pio
>>>>
>>>> Since each of these sets is staged, upstream testers will be able to say
>>>> "2.6.17-rc1 works, but 2.6.18-git1 doesn't", which gives us a lot of
>>>> good info.
>>>>
>>>>         Jeff
>>> So for those of us anxiously waiting for the above great enhancements
>>> it looks like it will be 5 months or so before it is in a released
>>> vanilla kernel?  ie. assuming 2 1/2 months per kernel release.
>> Heavens no :)
>>
>> The stages above just need to be separated out by a few 2.6.X-gitX or
>> 2.6.X-rcX releases.
>>
>>         Jeff
> 
> I'm confused.  You just poseted:
> 
>> Due to the merge window closing, the three pending patchsets will be in
>> 2.6.18.
> 
> That sure sounds like 5 months before it is in a released vanilla
> kernel.  ie. it has been taking about 10 weeks per kernel release. 
> 2.6.17 is likely to take another 8 weeks.  Then 10 weeks for 2.6.18 to
> come out.

Hopefully the releases won't take that long :)

	Jeff




  reply	other threads:[~2006-04-04 13:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-02  8:54 [PATCHSET] libata: improve ata_bus_probe failure handling, take 2 Tejun Heo
2006-04-02  8:54 ` [PATCH 6/7] libata: improve ata_bus_probe() Tejun Heo
2006-04-02 10:47   ` Jeff Garzik
2006-04-02  8:54 ` [PATCH 4/7] libata: add 5s sleep between resets Tejun Heo
2006-04-02 11:55   ` Tejun Heo
2006-04-02  8:54 ` [PATCH 3/7] libata: use SATA speed down in ata_drive_probe_reset() Tejun Heo
2006-04-02  8:54 ` [PATCH 1/7] libata: implement ata_dev_absent() Tejun Heo
2006-04-02  8:54 ` [PATCH 5/7] libata: implement ata_down_xfermask_limit() Tejun Heo
2006-04-02  8:54 ` [PATCH 2/7] libata: implement ap->sata_spd_limit and helpers Tejun Heo
2006-04-02 10:43   ` Jeff Garzik
2006-04-02 11:04     ` Tejun Heo
2006-04-02 11:18       ` Jeff Garzik
2006-04-02 11:53         ` Tejun Heo
2006-04-02  8:54 ` [PATCH 7/7] libata: consider disabled devices in ata_dev_xfermask() Tejun Heo
2006-04-02 14:35 ` [PATCHSET] libata: improve ata_bus_probe failure handling, take 2 Jeff Garzik
2006-04-03  9:37   ` Albert Lee
2006-04-03 10:38     ` Jeff Garzik
2006-04-03 14:37       ` Greg Freemyer
2006-04-03 16:20         ` Jeff Garzik
2006-04-04 13:02           ` Greg Freemyer
2006-04-04 13:11             ` Jeff Garzik [this message]
2006-04-04  5:02       ` Albert Lee
2006-04-03  9:43   ` [PATCH] libata-dev: irq-pio minor fix Albert Lee
2006-04-04 12:42     ` Jeff Garzik
2006-04-03 10:31   ` [PATCH] libata-dev: irq-pio minor fix 2 Albert Lee

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=4432709D.2080708@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=albertl@mail.com \
    --cc=greg.freemyer@gmail.com \
    --cc=htejun@gmail.com \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).