From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <tj@kernel.org>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
bugsbuggy@ymail.com
Subject: Re: [PATCH #upstream-fixes 1/2] pata_atiixp: update port enabledness test handling
Date: Mon, 02 Feb 2009 23:10:00 -0500 [thread overview]
Message-ID: <4987C398.50709@garzik.org> (raw)
In-Reply-To: <4984FB99.6000704@kernel.org>
Tejun Heo wrote:
> Tejun Heo wrote:
>> Port enabledness test fits much better into init_one() instead of
>> pre_reset(). The reason why these tests are in pre_reset() is purely
>> historical at this point. Move it to init_one(). This will help
>> further changes.
>>
>> Signed-off-by: Tejun Heo <tj@kernel.org>
>
> Jeff, the second one turned out to be unnecessary but this patch is
> worthy on its own. Can you please put
You mean upstream commit 16028232bf6dc5ed7e4bd341ef335f386229ad0b ?
Jeff
prev parent reply other threads:[~2009-02-03 4:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 6:27 [PATCH #upstream-fixes 1/2] pata_atiixp: update port enabledness test handling Tejun Heo
2009-01-16 6:32 ` Tejun Heo
2009-02-01 1:32 ` Tejun Heo
2009-02-03 4:10 ` Jeff Garzik [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=4987C398.50709@garzik.org \
--to=jeff@garzik.org \
--cc=bugsbuggy@ymail.com \
--cc=linux-ide@vger.kernel.org \
--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).