From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
davem@davemloft.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dmabounce: fix partial sync in dma_sync_single_* API
Date: Mon, 12 Apr 2010 20:35:36 +0100 [thread overview]
Message-ID: <20100412193536.GO3048@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20100405123847C.fujita.tomonori@lab.ntt.co.jp>
On Mon, Apr 05, 2010 at 12:39:32PM +0900, FUJITA Tomonori wrote:
> I don't have arm hardware that uses dmabounce so I can't confirm the
> problem but seems that dmabounce doesn't work for some drivers...
Patch reviews fine, except for one niggle. I too don't have hardware
I can test (well, I do except the kernel stopped supporting the UDA1341
audio codec on the SA1110 Neponset.)
> @@ -171,10 +172,17 @@ find_safe_buffer(struct dmabounce_device_info *device_info, dma_addr_t safe_dma_
> read_lock_irqsave(&device_info->lock, flags);
>
> list_for_each_entry(b, &device_info->safe_buffers, node)
> - if (b->safe_dma_addr == safe_dma_addr) {
> - rb = b;
> - break;
> - }
> + if (for_sync) {
> + if (b->safe_dma_addr <= safe_dma_addr &&
> + safe_dma_addr < b->safe_dma_addr + b->size) {
> + rb = b;
> + break;
> + }
> + } else
> + if (b->safe_dma_addr == safe_dma_addr) {
> + rb = b;
> + break;
> + }
This is the niggle; I don't like this indentation style. If you want to
indent this if () statement, then please format like this:
} else {
if (b->safe...) {
...
}
}
or format it as:
} else if (b->safe...) {
...
}
next prev parent reply other threads:[~2010-04-12 19:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 3:39 FUJITA Tomonori
2010-04-12 19:35 ` Russell King - ARM Linux [this message]
2010-04-13 5:27 ` FUJITA Tomonori
2010-04-27 22:50 ` FUJITA Tomonori
2010-04-29 11:34 ` Russell King - ARM Linux
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=20100412193536.GO3048@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=davem@davemloft.net \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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
all inboxes | Powered by JetHome®