From: Tejun Heo <tj@kernel.org>
To: Greg KH <greg@kroah.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
stable@kernel.org, Jeff Garzik <jeff@garzik.org>,
Thomas Jarosch <thomas.jarosch@intra2net.com>
Subject: Re: [stable] [PATCH] ahci: restore pci_intx() handling
Date: Thu, 17 Sep 2009 00:52:02 +0900 [thread overview]
Message-ID: <4AB109A2.5080504@kernel.org> (raw)
In-Reply-To: <20090916154807.GA27478@kroah.com>
Greg KH wrote:
> In the future, for stuff that you want sent to stable, can you also add:
> Cc: stable <stable@kernel.org>
> in this signed-off-by area? That way, when the patch hits Linus's tree,
> we get automatically notified of it and I don't have to dig back through
> log files to try to find out if your commit has made it in or not.
Ah... new protocol. Will do.
Thanks.
--
tejun
next prev parent reply other threads:[~2009-09-16 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 15:34 [PATCH] ahci: restore pci_intx() handling Tejun Heo
2009-09-16 15:48 ` [stable] " Greg KH
2009-09-16 15:52 ` Tejun Heo [this message]
2009-09-17 20:49 ` Jeff Garzik
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=4AB109A2.5080504@kernel.org \
--to=tj@kernel.org \
--cc=greg@kroah.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=stable@kernel.org \
--cc=thomas.jarosch@intra2net.com \
/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).