From: Jeff Garzik <jeff@garzik.org>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
akpm@osdl.org, torvalds@osdl.org
Subject: Re: [PATCH] libata-core: Fix simplex handling
Date: Fri, 02 Mar 2007 17:42:59 -0500 [thread overview]
Message-ID: <45E8A873.30604@garzik.org> (raw)
In-Reply-To: <20070301173646.4138981b@lxorguk.ukuu.org.uk>
Alan wrote:
> The initial simplex handling code is fooled if you suspend and resume.
> This also causes problems with some single channel controllers which
> claim to be simplex.
>
> The fix is fairly simple, instead of keeping a flag to remember if we
> gave away the simplex channel we remember the actual owner. As the owner
> is always part of the host_set we don't even need a refcount.
>
> Knowing the owner also means we can reassign simplex DMA channels in
> future hotplug code etc if we need to
>
> Signed-off-by: Alan Cox <alan@redhat.com>
> (and a signed-off for the patch I sent before while I remember)
applied
prev parent reply other threads:[~2007-03-02 22:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 17:36 [PATCH] libata-core: Fix simplex handling Alan
2007-03-02 22:42 ` 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=45E8A873.30604@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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).