From: Markus Elfring <Markus.Elfring@web.de>
To: Wolfram Sang <wsa@kernel.org>, Andrew Davis <afd@ti.com>,
Bartosz Golaszewski <brgl@bgdev.pl>,
linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
kernel-janitors@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [v2 2/2] i2c: davinci: Use struct name not type with devm_kzalloc()
Date: Thu, 8 Jun 2023 20:46:51 +0200 [thread overview]
Message-ID: <9039895e-830e-49fd-6761-d7a95659d2d2@web.de> (raw)
In-Reply-To: <ZIHZnMQHDyTsZx7O@shikoro>
>> Will the patch review attention grow anyhow for affected aspects?
>
> What are "affected aspects" in this case?
Example:
Linux patch requirements and corresponding coding style variations
Regards,
Markus
_______________________________________________
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 18:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 17:50 [PATCH v2 1/2] i2c: davinci: Use platform table macro over module_alias Andrew Davis
2023-05-15 17:50 ` Andrew Davis
2023-05-15 17:50 ` [PATCH v2 2/2] i2c: davinci: Use struct name not type with devm_kzalloc() Andrew Davis
2023-05-15 17:50 ` Andrew Davis
2023-05-16 14:45 ` Bartosz Golaszewski
2023-05-16 14:45 ` Bartosz Golaszewski
2023-06-07 9:29 ` Wolfram Sang
2023-06-07 9:29 ` Wolfram Sang
2023-06-08 9:42 ` Markus Elfring
2023-06-08 11:24 ` Wolfram Sang
2023-06-08 11:24 ` Wolfram Sang
2023-06-08 11:30 ` [v2 " Markus Elfring
2023-06-08 13:37 ` Wolfram Sang
2023-06-08 13:37 ` Wolfram Sang
2023-06-08 18:46 ` Markus Elfring [this message]
2023-05-16 14:46 ` [PATCH v2 1/2] i2c: davinci: Use platform table macro over module_alias Bartosz Golaszewski
2023-05-16 14:46 ` Bartosz Golaszewski
2023-06-07 9:32 ` Wolfram Sang
2023-06-07 9:32 ` Wolfram Sang
2023-06-23 8:27 ` Wolfram Sang
2023-06-23 8:27 ` Wolfram Sang
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=9039895e-830e-49fd-6761-d7a95659d2d2@web.de \
--to=markus.elfring@web.de \
--cc=afd@ti.com \
--cc=brgl@bgdev.pl \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 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.