All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Jeff Garzik <jeff@garzik.org>,
	linux-ide@vger.kernel.org, stable@kernel.org
Subject: Re: [stable] [PATCH -stable] libata: sync NCQ blacklist with	upstream
Date: Fri, 19 Oct 2007 11:33:57 +0900	[thread overview]
Message-ID: <47181795.8030705@gmail.com> (raw)
In-Reply-To: <20071011035553.GA31615@kroah.com>

Greg KH wrote:
> On Thu, Oct 11, 2007 at 12:41:46PM +0900, Tejun Heo wrote:
>> Greg KH wrote:
>>> On Thu, Oct 11, 2007 at 12:21:23PM +0900, Tejun Heo wrote:
>>>> Greg KH wrote:
>>>>> On Thu, Oct 11, 2007 at 10:55:15AM +0900, Tejun Heo wrote:
>>>>>> Synchronize NCQ blacklist with the current upstream.
>>>>> Which -stable tree is this for, 2.6.22 or 2.6.23?
>>>> It's against 2.6.23.
>>> Ok, but things only go into -stable after they are already in Linus's
>>> tree, which hasn't happened yet...
>>>
>>> So what is considered "upstream" here?  Jeff's tree?
>> Yeah, except for one entry, all others are in libata-dev#upstream which
>> will be pulled when -rc1 opens.  I'll ping you back when they actually
>> get merged.
> 
> Thanks, that would help out a lot.

Alright, those changes are in Linus's tree now.

Thanks.

-- 
tejun

      reply	other threads:[~2007-10-19  2:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11  1:55 [PATCH -stable] libata: sync NCQ blacklist with upstream Tejun Heo
2007-10-11  2:57 ` [stable] " Greg KH
2007-10-11  3:21   ` Tejun Heo
2007-10-11  3:32     ` Greg KH
2007-10-11  3:41       ` Tejun Heo
2007-10-11  3:55         ` Greg KH
2007-10-19  2:33           ` Tejun Heo [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=47181795.8030705@gmail.com \
    --to=htejun@gmail.com \
    --cc=greg@kroah.com \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.