From: Arnd Bergmann <arnd@arndb.de>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Russell King <linux@armlinux.org.uk>,
Christoph Hellwig <hch@lst.de>, Arnd Bergmann <arnd@arndb.de>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
kernel-janitors <kernel-janitors@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dma-mapping: update comment after dmabounce removal
Date: Fri, 22 Jul 2022 14:50:20 +0200 [thread overview]
Message-ID: <CAK8P3a04pfMoTbWDSdUPYXhXi03i3AjWM1B-8j2Z1OJKRmC14A@mail.gmail.com> (raw)
In-Reply-To: <20220720190208.11270-1-lukas.bulwahn@gmail.com>
On Wed, Jul 20, 2022 at 9:02 PM Lukas Bulwahn <lukas.bulwahn@gmail.com> wrote:
>
> Commit e3217540c271 ("ARM/dma-mapping: remove dmabounce") removes the
> config DMABOUNCE. A comment to the function __dma_page_cpu_to_dev() refers
> to this removed config DMABOUNCE.
>
> Remove the obsolete explanation, but keep the recommendation not to use
> __dma_page_cpu_to_dev() and use dma_sync_* functions instead.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
Thanks!
Acked-by: Arnd Bergmann <arnd@arndb.de>
The e3217540c271 commit is only in Christoph's dma-mapping tree, so this would
ideally get applied on top before the merge window.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Russell King <linux@armlinux.org.uk>,
Christoph Hellwig <hch@lst.de>, Arnd Bergmann <arnd@arndb.de>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
kernel-janitors <kernel-janitors@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dma-mapping: update comment after dmabounce removal
Date: Fri, 22 Jul 2022 14:50:20 +0200 [thread overview]
Message-ID: <CAK8P3a04pfMoTbWDSdUPYXhXi03i3AjWM1B-8j2Z1OJKRmC14A@mail.gmail.com> (raw)
In-Reply-To: <20220720190208.11270-1-lukas.bulwahn@gmail.com>
On Wed, Jul 20, 2022 at 9:02 PM Lukas Bulwahn <lukas.bulwahn@gmail.com> wrote:
>
> Commit e3217540c271 ("ARM/dma-mapping: remove dmabounce") removes the
> config DMABOUNCE. A comment to the function __dma_page_cpu_to_dev() refers
> to this removed config DMABOUNCE.
>
> Remove the obsolete explanation, but keep the recommendation not to use
> __dma_page_cpu_to_dev() and use dma_sync_* functions instead.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
Thanks!
Acked-by: Arnd Bergmann <arnd@arndb.de>
The e3217540c271 commit is only in Christoph's dma-mapping tree, so this would
ideally get applied on top before the merge window.
Arnd
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-07-22 12:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 19:02 [PATCH] dma-mapping: update comment after dmabounce removal Lukas Bulwahn
2022-07-20 19:02 ` Lukas Bulwahn
2022-07-22 12:50 ` Arnd Bergmann [this message]
2022-07-22 12:50 ` Arnd Bergmann
2022-07-22 15:04 ` Christoph Hellwig
2022-07-22 15:04 ` Christoph Hellwig
2022-07-22 15:15 ` Christoph Hellwig
2022-07-22 15:15 ` Christoph Hellwig
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=CAK8P3a04pfMoTbWDSdUPYXhXi03i3AjWM1B-8j2Z1OJKRmC14A@mail.gmail.com \
--to=arnd@arndb.de \
--cc=hch@lst.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lukas.bulwahn@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.