From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: fix pci_set_consistent_dma_mask for dmabounce devices
Date: Wed, 1 Sep 2010 09:57:38 +0100 [thread overview]
Message-ID: <20100901085738.GJ8142@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <m3sk1yzkjw.fsf@intrepid.localdomain>
On Sat, Aug 28, 2010 at 07:58:11PM +0200, Krzysztof Halasa wrote:
> What's the outcome of the following?
>
> Russell, are you going to apply it as is, or is a better (short-term)
> fix being made?
I want to see a better solution to this first - without which we'll
apply this hack and then quietly forget about the problem.
next prev parent reply other threads:[~2010-09-01 8:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 8:51 [PATCH] arm: fix pci_set_consistent_dma_mask for dmabounce devices FUJITA Tomonori
2010-08-28 17:58 ` Krzysztof Halasa
2010-09-01 8:57 ` Russell King - ARM Linux [this message]
2010-09-02 2:50 ` FUJITA Tomonori
2010-09-02 5:59 ` Richard Cochran
2010-09-05 10:50 ` Eric Miao
2010-09-05 11:21 ` Russell King - ARM Linux
2010-09-05 11:58 ` Eric Miao
2010-09-05 11:25 ` Russell King - ARM Linux
2010-09-05 23:32 ` FUJITA Tomonori
2010-09-14 21:23 ` Krzysztof Halasa
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=20100901085738.GJ8142@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).