From: Kalle Valo <kvalo@codeaurora.org>
To: Arvind Yadav <arvind.yadav.cs@gmail.com>
Cc: sgruszka@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 00/10] Constify attribute_group structures
Date: Tue, 25 Jul 2017 15:55:40 +0300 [thread overview]
Message-ID: <87fudkiskz.fsf@codeaurora.org> (raw)
In-Reply-To: <1499758370-24871-1-git-send-email-arvind.yadav.cs@gmail.com> (Arvind Yadav's message of "Tue, 11 Jul 2017 13:02:48 +0530")
Arvind Yadav <arvind.yadav.cs@gmail.com> writes:
> attribute_groups are not supposed to change at runtime. So mark the
> non-const structs as const.
>
> Arvind Yadav (10):
> [PATCH v2 01/10] net: cdc_ncm: constify attribute_group structures.
> [PATCH v2 02/10] net: can: at91_can: constify attribute_group structures.
> [PATCH v2 03/10] net: can: janz-ican3: constify attribute_group structures.
> [PATCH v2 04/10] wireless: ipw2200: constify attribute_group structures.
> [PATCH v2 05/10] wireless: ipw2100: constify attribute_group structures.
> [PATCH v2 06/10] wireless: iwlegacy: constify attribute_group structures.
> [PATCH v2 07/10] wireless: iwlegacy: Constify attribute_group structures.
> [PATCH v2 08/10] arcnet: com20020-pci: constify attribute_group structures.
> [PATCH v2 09/10] net: bonding: constify attribute_group structures.
> [PATCH v2 10/10] net: chelsio: cxgb3: constify attribute_group structures.
Via which tree were you planning to push these? Is it ok if I take the
wireless patches to my tree?
--
Kalle Valo
next prev parent reply other threads:[~2017-07-25 12:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 7:32 [PATCH v2 00/10] Constify attribute_group structures Arvind Yadav
2017-07-11 7:32 ` [PATCH v2 06/10] wireless: iwlegacy: constify " Arvind Yadav
2017-07-11 7:32 ` [PATCH v2 07/10] wireless: iwlegacy: Constify " Arvind Yadav
2017-07-25 12:55 ` Kalle Valo [this message]
2017-07-26 6:35 ` [PATCH v2 00/10] " Arvind Yadav
2017-07-26 6:36 ` Arvind Yadav
-- strict thread matches above, loose matches on Subject: below --
2017-07-11 7:37 Arvind Yadav
2017-07-11 7:36 Arvind Yadav
2017-07-11 7:34 Arvind Yadav
2017-07-11 7:31 Arvind Yadav
2017-07-11 7:29 Arvind Yadav
2017-07-11 7:48 ` Marc Kleine-Budde
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=87fudkiskz.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=arvind.yadav.cs@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sgruszka@redhat.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.