public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-ide@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Subject: Re: [git patches] libata updates for 2.6.33
Date: Mon, 07 Dec 2009 11:39:31 -0500	[thread overview]
Message-ID: <4B1D2FC3.4090003@garzik.org> (raw)
In-Reply-To: <4B1D02F9.4000503@ru.mvista.com>

On 12/07/2009 08:28 AM, Sergei Shtylyov wrote:
> Hello.
>
> Jeff Garzik wrote:
>
>> Nothing world-shakingly-notable. Notable notables:
>
>> - TRIM work from Christoph and mkp, to make SSD life a bit better
>> - PATA fixes and updates from Bart and Alan
>> - long overdue removal of 'experimental' tag from PATA driver submenu
>> in Kconfig
>> - various bug fixes and minor updates
>
>> Please pull from 'upstream-linus' branch of
>> master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
>> upstream-linus
>
>> to receive the following updates:
>
> [...]
>
>> Alan Cox (6):
>> pata_via: Blacklist some combinations of Transcend Flash and via
>> pata_sis: Implement MWDMA for the UDMA 133 capable chips
>
> Unfortunately, this patch contains a coding mistake. Probably too late
> to correct it now though Linus hasn't pulled as yet...

Well, absence of a push does not necessarily imply absence of a pull :) 
  In fact it seems pretty normal these days that Linus collects a bunch 
of pull requests, and then pushes them out later all in one batch.

But we can revert, absolutely, given the feedback from you and Bart...

	Jeff





      reply	other threads:[~2009-12-07 16:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-06 21:07 [git patches] libata updates for 2.6.33 Jeff Garzik
2009-12-07 13:28 ` Sergei Shtylyov
2009-12-07 16:39   ` Jeff Garzik [this message]

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=4B1D2FC3.4090003@garzik.org \
    --to=jeff@garzik.org \
    --cc=akpm@linux-foundation.org \
    --cc=bzolnier@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sshtylyov@ru.mvista.com \
    --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