From: Larry Finger <Larry.Finger@lwfinger.net>
To: Pavel Roskin <proski@gnu.org>
Cc: linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH 1/2] b43legacy: report core number
Date: Tue, 26 Jul 2011 10:57:55 -0500 [thread overview]
Message-ID: <4E2EE403.5090207@lwfinger.net> (raw)
In-Reply-To: <20110726153648.24611.49190.stgit@mj.roinet.com>
On 07/26/2011 10:36 AM, Pavel Roskin wrote:
> Signed-off-by: Pavel Roskin<proski@gnu.org>
> ---
> 0 files changed, 0 insertions(+), 0 deletions(-)
Very informative diffstat! :)
>
> diff --git a/drivers/net/wireless/b43legacy/main.c b/drivers/net/wireless/b43legacy/main.c
> index ffa4671..224991a 100644
> --- a/drivers/net/wireless/b43legacy/main.c
> +++ b/drivers/net/wireless/b43legacy/main.c
> @@ -3785,7 +3785,8 @@ static int b43legacy_wireless_init(struct ssb_device *dev)
> INIT_WORK(&wl->beacon_update_trigger, b43legacy_beacon_update_trigger_work);
>
> ssb_set_devtypedata(dev, wl);
> - b43legacyinfo(wl, "Broadcom %04X WLAN found\n", dev->bus->chip_id);
> + b43legacyinfo(wl, "Broadcom %04X WLAN found (core revision %u)\n",
> + dev->bus->chip_id, dev->id.revision);
> err = 0;
> out:
> return err;
ACKed-by: Larry Finger <Larry.Finger@lwfinger.net>
next prev parent reply other threads:[~2011-07-26 15:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 15:36 [PATCH 1/2] b43legacy: report core number Pavel Roskin
2011-07-26 15:36 ` [PATCH 2/2] b43legacy: remove asm/atomic.h includes as suggested by checkpatch.pl Pavel Roskin
2011-07-26 15:55 ` Larry Finger
2011-07-26 15:57 ` Larry Finger [this message]
2011-07-26 16:08 ` [PATCH 1/2] b43legacy: report core number Pavel Roskin
2011-08-03 15:55 ` Kalle Valo
2011-08-03 18:26 ` Pavel Roskin
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=4E2EE403.5090207@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=proski@gnu.org \
/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).