From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Arvind Yadav <arvind.yadav.cs@gmail.com>,
davem@davemloft.net, wg@grandegger.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 00/10] Constify attribute_group structures
Date: Tue, 11 Jul 2017 09:48:20 +0200 [thread overview]
Message-ID: <fec4d3c9-1ac8-c752-b8a5-3f446042fe4e@pengutronix.de> (raw)
In-Reply-To: <1499758158-24741-1-git-send-email-arvind.yadav.cs@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 629 bytes --]
On 07/11/2017 09:29 AM, Arvind Yadav wrote:
> attribute_groups are not supposed to change at runtime. So mark the
> non-const structs as const.
[...]
> drivers/net/can/at91_can.c | 2 +-
> drivers/net/can/janz-ican3.c | 2 +-
For the can drivers:
Acked-by: Marc Kleine-Budde <mkl@pengutronix.de>
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-07-11 7:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 7:29 [PATCH v2 00/10] Constify attribute_group structures Arvind Yadav
2017-07-11 7:29 ` [PATCH v2 02/10] net: can: at91_can: constify " Arvind Yadav
2017-07-11 7:29 ` [PATCH v2 03/10] net: can: janz-ican3: " Arvind Yadav
2017-07-11 7:48 ` Marc Kleine-Budde [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-07-11 7:37 [PATCH v2 00/10] Constify " Arvind Yadav
2017-07-11 7:36 Arvind Yadav
2017-07-11 7:34 Arvind Yadav
2017-07-11 7:32 Arvind Yadav
2017-07-25 12:55 ` Kalle Valo
2017-07-26 6:35 ` Arvind Yadav
2017-07-26 6:36 ` Arvind Yadav
2017-07-11 7:31 Arvind Yadav
2017-07-11 7:22 Arvind Yadav
2017-07-11 17:34 ` David Miller
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=fec4d3c9-1ac8-c752-b8a5-3f446042fe4e@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=arvind.yadav.cs@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wg@grandegger.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).