From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Mikael Pettersson <mikpe@it.uu.se>,
kurt@roeckx.be, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.25-rc6] sata_promise: fix hardreset hotplug events, take 2
Date: Tue, 25 Mar 2008 12:32:49 +0900 [thread overview]
Message-ID: <47E87261.4020603@gmail.com> (raw)
In-Reply-To: <47E86580.6050206@gmail.com>
Tejun Heo wrote:
> Jeff Garzik wrote:
>> Tejun Heo wrote:
>>> Acked-by: Tejun Heo <htejun@gmail.com>
>>>
>>> Jeff, do you want to merge this first? If so, I'll update the
>>> prefer-hardreset and cleanup-sht-ops patchsets; otherwise, I'll massage
>>> this patch a bit so that it fits on top of those two patchsets.
>>
>> I just merged it into #upstream-fixes (answering your question)... what
>> is your preferred method of sync'ing at this point?
>
> Heh... me refreshing the patchset again. Doing it right now.
Okay, updated. Please pull from
http://git.kernel.org/?p=linux/kernel/git/tj/libata-dev.git;a=shortlog;h=cleanup-sht-ops
git://git.kernel.org/pub/scm/linux/kernel/git/tj/libata-dev.git cleanup-sht-ops
It's now on top of the current #upstream-fixes (4cde32fc) and contains
the followings.
* prefer-hardreset patchset
* PCI-device-should-be-powered-up-before-being-accssed patch
* cleanup-sht-ops patchset
Thanks.
--
tejun
next prev parent reply other threads:[~2008-03-25 3:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-22 14:21 [PATCH 2.6.25-rc6] sata_promise: fix hardreset hotplug quirk Mikael Pettersson
2008-03-23 3:21 ` Tejun Heo
2008-03-23 10:30 ` Mikael Pettersson
2008-03-23 12:07 ` Tejun Heo
2008-03-23 17:41 ` [PATCH 2.6.25-rc6] sata_promise: fix hardreset hotplug events, take 2 Mikael Pettersson
2008-03-24 2:19 ` Tejun Heo
2008-03-25 2:32 ` Jeff Garzik
2008-03-25 2:37 ` Tejun Heo
2008-03-25 3:32 ` Tejun Heo [this message]
2008-03-25 3:53 ` Jeff Garzik
2008-03-25 2:31 ` Jeff Garzik
2008-04-11 21:11 ` Kurt Roeckx
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=47E87261.4020603@gmail.com \
--to=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=kurt@roeckx.be \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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.