From: Michael Walle <michael@walle.cc>
To: Michael Walle <michael@walle.cc>
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>,
linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] i2c: at91: use dma safe buffers
Date: Wed, 04 May 2022 22:48:30 +0200 [thread overview]
Message-ID: <23c66c4077d87ca484c589e1033c26fd@walle.cc> (raw)
In-Reply-To: <YnLgpyvVjcbiCs7m@kunai>
Am 2022-05-04 22:23, schrieb Wolfram Sang:
> BTW, my name is Wolfram.
Sorry :/
-michael
WARNING: multiple messages have this Message-ID (diff)
From: Michael Walle <michael@walle.cc>
To: Michael Walle <michael@walle.cc>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
Codrin Ciubotariu <codrin.ciubotariu@microchip.com>,
Claudiu Beznea <claudiu.beznea@microchip.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] i2c: at91: use dma safe buffers
Date: Wed, 04 May 2022 22:48:30 +0200 [thread overview]
Message-ID: <23c66c4077d87ca484c589e1033c26fd@walle.cc> (raw)
In-Reply-To: <YnLgpyvVjcbiCs7m@kunai>
Am 2022-05-04 22:23, schrieb Wolfram Sang:
> BTW, my name is Wolfram.
Sorry :/
-michael
_______________________________________________
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-05-04 20:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 15:08 [PATCH v2] i2c: at91: use dma safe buffers Michael Walle
2022-04-07 15:08 ` Michael Walle
2022-05-02 21:36 ` Michael Walle
2022-05-02 21:36 ` Michael Walle
2022-05-04 20:23 ` Wolfram Sang
2022-05-04 20:23 ` Wolfram Sang
2022-05-04 20:48 ` Michael Walle [this message]
2022-05-04 20:48 ` Michael Walle
2022-05-05 14:51 ` Nathan Chancellor
2022-05-05 14:51 ` Nathan Chancellor
2022-05-05 15:11 ` Michael Walle
2022-05-05 15:11 ` Michael Walle
2022-05-05 15:18 ` Nathan Chancellor
2022-05-05 15:18 ` Nathan Chancellor
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=23c66c4077d87ca484c589e1033c26fd@walle.cc \
--to=michael@walle.cc \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=codrin.ciubotariu@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@microchip.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.