From: Jeff Garzik <jeff@garzik.org>
To: Arnaud Patard <apatard@mandriva.com>
Cc: Tejun Heo <htejun@gmail.com>, linux-ide@vger.kernel.org
Subject: Re: [PATCH] Fix libata resource conflict for legacy mode
Date: Tue, 19 Sep 2006 00:27:07 -0400 [thread overview]
Message-ID: <450F719B.1020002@garzik.org> (raw)
In-Reply-To: <m3zmcxgqu6.fsf@anduin.mandriva.com>
Arnaud Patard wrote:
> When the libata is trying to handle legacy ide ports (0x1f0 for instance), it
> doesn't take care if the resource has childs or not.
> The result is that this situation :
> 0100-01fe : pnp 00:09
> 0170-0177 : libata
> 01f0-01f7 : libata
>
> is seen as conflict, which is wrong.
> The proposed fix is to detect childs and in this case, look at which child is
> conflicting.
>
> Signed-off-by: Arnaud Patard <apatard@mandriva.com>
Applied. For the future, please inline both the patch description, and
the patch itself. I had to apply this manually, rather than use the
usual scripts.
For more info read:
Documentation/SubmittingPatches
http://linux.yyz.us/patch-format.html
Jeff
prev parent reply other threads:[~2006-09-19 4:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 13:16 [PATCH] Fix libata resource conflict for legacy mode Arnaud Patard
2006-09-18 13:48 ` Tejun Heo
2006-09-18 15:02 ` Arnaud Patard
2006-09-18 16:17 ` Tejun Heo
2006-09-19 4:27 ` 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=450F719B.1020002@garzik.org \
--to=jeff@garzik.org \
--cc=apatard@mandriva.com \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.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).