From: Wolfram Sang <wsa@the-dreams.de>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Kevin Hilman <khilman@kernel.org>, Sekhar Nori <nsekhar@ti.com>,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
kernel-janitors@vger.kernel.org, Andrew Davis <afd@ti.com>
Subject: Re: [linux-i2c] Patch notification: DaVinci: 2 patches updated
Date: Thu, 8 Jun 2023 22:23:39 +0200 [thread overview]
Message-ID: <ZII4y9PfM/yBdvU+@shikoro> (raw)
In-Reply-To: <4bf54a0d-f525-5dab-1e7e-756e71a7267a@web.de>
[-- Attachment #1.1: Type: text/plain, Size: 316 bytes --]
> If I look at patches which I contributed for the software area “I2C”,
> I got the impression that further constructive feedback will be helpful also for
> six change possibilities from days like the following.
Yes, you are right. these patches need feedback. This is why I haven't
applied them yet.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
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:[~2023-06-08 20:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <168613080300.11524.2783831689498520603@legolas.ozlabs.org>
2023-06-08 7:09 ` [linux-i2c] Patch notification: DaVinci: 2 patches updated Markus Elfring
2023-06-08 7:47 ` Wolfram Sang
2023-06-08 8:21 ` Markus Elfring
2023-06-08 11:26 ` Wolfram Sang
2023-06-08 11:48 ` Markus Elfring
2023-06-08 13:41 ` Wolfram Sang
2023-06-08 19:03 ` Markus Elfring
2023-06-08 20:23 ` Wolfram Sang [this message]
2023-06-09 6:26 ` Markus Elfring
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=ZII4y9PfM/yBdvU+@shikoro \
--to=wsa@the-dreams.de \
--cc=Markus.Elfring@web.de \
--cc=afd@ti.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=nsekhar@ti.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 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).