From: Tejun Heo <htejun@gmail.com>
To: Jeroen Janssen <jeroen.janssen@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
stable@kernel.org
Subject: Re: [PATCH] sata_via: add missing PM hooks
Date: Tue, 08 May 2007 12:27:05 +0200 [thread overview]
Message-ID: <46405079.6070300@gmail.com> (raw)
In-Reply-To: <e34e42440705080254v2fdd5069yccb946f71dec5231@mail.gmail.com>
Jeroen Janssen wrote:
> Hi,
>
> Any idea how I can track that this has been picked up/applied (I
> looked at some of the git repositories on kernel.org, but as far as I
> can tell, this patch is not in yet).
It's still pending. What usually happens is Jeff replying with the body
saying 'applied' and the patch gets into libata-dev#upstream or
#upstream-fixes and then merged into Linus's tree. For stable release,
after Jeff acks it, Greg or any other stable team member picks it up and
writes a formatted mail about it to everyone on the S-O-B: or Cc: list
and stable mailing list. So, nope, it hasn't happend yet but you'll get
a notice when it happens.
--
tejun
next prev parent reply other threads:[~2007-05-08 10:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 13:30 [PATCH] sata_via: add missing PM hooks Tejun Heo
2007-05-08 9:54 ` Jeroen Janssen
2007-05-08 10:27 ` Tejun Heo [this message]
2007-05-10 0:17 ` Jeff Garzik
2007-05-17 1:52 ` patch sata_via-add-missing-pm-hooks.patch queued to 2.6.21-stable tree chrisw
-- strict thread matches above, loose matches on Subject: below --
2007-05-03 12:42 VIA VT6420 SATA suspend/resume problem in 2.6.20? Jeroen Janssen
2007-05-03 14:45 ` Tejun Heo
2007-05-04 8:22 ` Jeroen Janssen
2007-05-04 9:03 ` [PATCH] sata_via: add missing PM hooks Tejun Heo
2007-05-04 13:21 ` Jeroen Janssen
2007-05-04 13:25 ` Tejun Heo
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=46405079.6070300@gmail.com \
--to=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=jeroen.janssen@gmail.com \
--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 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).