linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo Van Doorn <ivdoorn@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org,
	Gertjan van Wingerde <gwingerde@gmail.com>
Subject: Re: [PATCH] rt2x00: update fw version info in wiphy struct
Date: Thu, 29 Jul 2010 21:58:45 +0200	[thread overview]
Message-ID: <AANLkTi=BMeQexF+LjRYV=xfZFMLniovorLED80kRwKrr@mail.gmail.com> (raw)
In-Reply-To: <1280425899-20943-1-git-send-email-linville@tuxdriver.com>

On Thu, Jul 29, 2010 at 7:51 PM, John W. Linville
<linville@tuxdriver.com> wrote:
> This makes the information available through ethtool...
>
> Signed-off-by: John W. Linville <linville@tuxdriver.com>

Acked-by: Ivo van Doorn <IvDoorn@gmail.com>

> ---
>  drivers/net/wireless/rt2x00/rt2x00firmware.c |    3 +++
>  1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/net/wireless/rt2x00/rt2x00firmware.c b/drivers/net/wireless/rt2x00/rt2x00firmware.c
> index b818a43..f0e1eb7 100644
> --- a/drivers/net/wireless/rt2x00/rt2x00firmware.c
> +++ b/drivers/net/wireless/rt2x00/rt2x00firmware.c
> @@ -63,6 +63,9 @@ static int rt2x00lib_request_firmware(struct rt2x00_dev *rt2x00dev)
>
>        INFO(rt2x00dev, "Firmware detected - version: %d.%d.\n",
>             fw->data[fw->size - 4], fw->data[fw->size - 3]);
> +       snprintf(rt2x00dev->hw->wiphy->fw_version,
> +                       sizeof(rt2x00dev->hw->wiphy->fw_version), "%d.%d",
> +                       fw->data[fw->size - 4], fw->data[fw->size - 3]);
>
>        retval = rt2x00dev->ops->lib->check_firmware(rt2x00dev, fw->data, fw->size);
>        switch (retval) {
> --
> 1.7.1.1
>
>

      reply	other threads:[~2010-07-29 19:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-29 17:51 [PATCH] rt2x00: update fw version info in wiphy struct John W. Linville
2010-07-29 19:58 ` Ivo Van Doorn [this message]

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='AANLkTi=BMeQexF+LjRYV=xfZFMLniovorLED80kRwKrr@mail.gmail.com' \
    --to=ivdoorn@gmail.com \
    --cc=gwingerde@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).