From: Kalle Valo <kvalo@codeaurora.org>
To: Arvind Yadav <arvind.yadav.cs@gmail.com>
Cc: davem@davemloft.net, stas.yakovlev@gmail.com,
sgruszka@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [v3,04/10] ipw2200: constify attribute_group structures
Date: Fri, 28 Jul 2017 15:06:11 +0000 (UTC) [thread overview]
Message-ID: <20170728150611.96B1A60884@smtp.codeaurora.org> (raw)
In-Reply-To: <1500371102-14758-1-git-send-email-arvind.yadav.cs@gmail.com>
Arvind Yadav <arvind.yadav.cs@gmail.com> wrote:
> attribute_group are not supposed to change at runtime. All functions
> working with attribute_group provided by <linux/sysfs.h> work
> with const attribute_group. So mark the non-const structs as const.
>
> Signed-off-by: Arvind Yadav <arvind.yadav.cs@gmail.com>
4 patches applied to wireless-drivers-next.git, thanks.
17830147c40a mwifiex: fix spelling mistake: "Insuffient" -> "Insufficient"
185ffc194800 ipw2100: don't return positive values to PCI probe on error
af643fe9bbe0 zd1211rw: fix spelling mistake 'hybernate' -> 'hibernate'
e66d70b789d1 brcmfmac: constify pci_device_id
--
https://patchwork.kernel.org/patch/9847373/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2017-07-28 15:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 9:44 [PATCH v3 04/10] wireless: ipw2200: constify attribute_group structures Arvind Yadav
2017-07-18 9:45 ` [PATCH v3 05/10] wireless: ipw2100: " Arvind Yadav
2017-07-18 9:45 ` [PATCH v3 06/10] wireless: iwlegacy: " Arvind Yadav
2017-07-18 9:45 ` [PATCH v3 07/10] wireless: iwlegacy: Constify " Arvind Yadav
2017-07-28 15:06 ` Kalle Valo [this message]
2017-07-28 15:08 ` [v3,04/10] ipw2200: constify " Kalle Valo
2017-07-28 16:54 ` Kalle Valo
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=20170728150611.96B1A60884@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=arvind.yadav.cs@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sgruszka@redhat.com \
--cc=stas.yakovlev@gmail.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).