From: "Arend van Spriel" <arend@broadcom.com>
To: "Stephen Hemminger" <shemminger@vyatta.com>
Cc: "John W.Linville" <linville@tuxdriver.com>,
"Franky (Zhenhui) Lin" <frankyl@broadcom.com>,
"Pieter-Paul Giesberts" <pieterpg@broadcom.com>,
"Alwin Beukers" <alwin@broadcom.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] brcm80211: make ethtool_ops const
Date: Thu, 5 Jan 2012 11:07:47 +0100 [thread overview]
Message-ID: <4F057673.8000807@broadcom.com> (raw)
In-Reply-To: <20120104145251.5102b435@nehalam.linuxnetplumber.net>
On 01/04/2012 11:52 PM, Stephen Hemminger wrote:
> All usage of ethtool_ops should be const; also add comma at end
> of initializer list.
>
> Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
> ---
> Patch against net-next
Assuming net-next and wireless-next are in sync.
Acked-by: Arend van Spriel <arend@broadcom.com>
Gr. AvS
parent reply other threads:[~2012-01-05 10:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20120104145251.5102b435@nehalam.linuxnetplumber.net>]
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=4F057673.8000807@broadcom.com \
--to=arend@broadcom.com \
--cc=alwin@broadcom.com \
--cc=frankyl@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=pieterpg@broadcom.com \
--cc=shemminger@vyatta.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).