From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <tj@kernel.org>
Cc: Christoph Egger <siccegge@stud.informatik.uni-erlangen.de>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
Reinhard.Tartler@informatik.uni-erlangen.de
Subject: Re: [PATCH #upstream-fixes] libata-sff: remove CONFIG_NO_ATA_LEGACY
Date: Wed, 20 Jan 2010 23:32:49 -0500 [thread overview]
Message-ID: <4B57D8F1.8040504@pobox.com> (raw)
In-Reply-To: <4B579C85.7010008@kernel.org>
On 01/20/2010 07:15 PM, Tejun Heo wrote:
> Oops, Jeff, please send this #upstream. I was thinking #upstream but
> my fingers had their own mind. Thanks.
yep, definitely #upstream material...
next prev parent reply other threads:[~2010-01-21 4:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 14:29 Unreferenced config in kernel (libata-sff.c) source (NO_ATA_LEGACY) Christoph Egger
2010-01-21 0:14 ` [PATCH #upstream-fixes] libata-sff: remove CONFIG_NO_ATA_LEGACY Tejun Heo
2010-01-21 0:15 ` Tejun Heo
2010-01-21 4:32 ` Jeff Garzik [this message]
2010-01-21 12:04 ` Alan Cox
2010-01-22 0:48 ` 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=4B57D8F1.8040504@pobox.com \
--to=jgarzik@pobox.com \
--cc=Reinhard.Tartler@informatik.uni-erlangen.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=siccegge@stud.informatik.uni-erlangen.de \
--cc=tj@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).