From: "Christian König" <christian.koenig@amd.com>
To: Wolfram Sang <wsa@kernel.org>, Michael Walle <michael@walle.cc>,
Codrin Ciubotariu <codrin.ciubotariu@microchip.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Beznea <claudiu.beznea@microchip.com>,
Sumit Semwal <sumit.semwal@linaro.org>,
linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org,
stable@vger.kernel.org
Subject: Re: [PATCH] i2c: at91: use dma safe buffers
Date: Fri, 4 Mar 2022 09:54:24 +0100 [thread overview]
Message-ID: <dbb0f319-5e54-8a86-fcee-2c88c9891898@amd.com> (raw)
In-Reply-To: <YiHRGa5bDJAuBuHj@shikoro>
Am 04.03.22 um 09:43 schrieb Wolfram Sang:
>> I'm getting quite a bunch of unrelated mails because the regex is not the
>> best.
> I can imagine!
>
>> On the other hand the framework is used in a lot of drivers and I do want to
>> be notified when they mess with their interfaces.
> Sure thing. I am convinced the regex can be improved to ensure that to a
> high degree. I think it is also less work for you than asking people to
> rename their variable all the time :)
Well not all the time. It's just that you absolutely hit the nail on the
head with the name.
The local variable for the DMA-buf handle is just nearly always named
dma_buf or dmabuf in the drivers.
Christian.
>
>> Going to take a another look at that when I have time.
> Thank you!
>
next prev parent reply other threads:[~2022-03-04 8:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 16:17 [PATCH] i2c: at91: use dma safe buffers Michael Walle
2022-03-04 7:35 ` Christian König
2022-03-04 8:04 ` Wolfram Sang
2022-03-04 8:10 ` Christian König
2022-03-04 8:43 ` Wolfram Sang
2022-03-04 8:54 ` Christian König [this message]
2022-03-28 7:35 ` Michael Walle
2022-04-05 9:23 ` Codrin.Ciubotariu
2022-04-05 9:38 ` Michael Walle
2022-04-05 10:02 ` Codrin.Ciubotariu
2022-04-05 11:09 ` Michael Walle
2022-04-05 13:58 ` Codrin.Ciubotariu
2022-04-05 14:08 ` Michael Walle
2022-04-07 11:50 ` Codrin.Ciubotariu
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=dbb0f319-5e54-8a86-fcee-2c88c9891898@amd.com \
--to=christian.koenig@amd.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=codrin.ciubotariu@microchip.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=michael@walle.cc \
--cc=nicolas.ferre@microchip.com \
--cc=stable@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=wsa@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).