From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: akpm@osdl.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata-core/sff: Fix multiple assumptions about DMA
Date: Sat, 09 Jun 2007 22:43:47 -0400 [thread overview]
Message-ID: <466B6563.9030107@garzik.org> (raw)
In-Reply-To: <20070607161915.2dbe3511@the-village.bc.nu>
Alan Cox wrote:
> The ata IRQ ack functions are only used when debugging. Unfortunately
> almost every controller that calls them can cause crashes in some
> configurations as there are missing checks for bmdma presence.
>
> In addition ata_port_start insists of installing DMA buffers and pad
> buffers for controllers regardless. The SFF controllers actually need to
> make that decision dynamically at controller setup time and all need the
> same helper - so we add ata_sff_port_start. Future patches will switch
> the SFF drivers to use this.
>
> Signed-off-by: Alan Cox <alan@redhat.com>
applied to #upstream-fixes
prev parent reply other threads:[~2007-06-10 2:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 15:19 [PATCH] libata-core/sff: Fix multiple assumptions about DMA Alan Cox
2007-06-10 2:43 ` 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=466B6563.9030107@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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).