From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
To: Michael Buesch <mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Stefano Brivio <st3-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org>,
Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org,
Larry Finger
<Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
Subject: Re: [PATCH] bcm43xx: fix unexpected LED control values in BCM4303 sprom
Date: Tue, 31 Oct 2006 22:49:42 -0500 [thread overview]
Message-ID: <20061101034936.GD9309@tuxdriver.com> (raw)
In-Reply-To: <200610181637.08698.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
On Wed, Oct 18, 2006 at 04:37:08PM +0200, Michael Buesch wrote:
> > @@ -257,7 +263,11 @@ void bcm43xx_leds_update(struct bcm43xx_
> > continue;
> > #endif /* CONFIG_BCM43XX_DEBUG */
> > default:
> > - assert(0);
> > + if (bcm43xx_max_led_err) {
> > + printkl(KERN_INFO PFX "Bad value in leds_update,"
> > + " led->behaviour: 0x%x\n", led->behaviour);
> > + --bcm43xx_max_led_err;
> > + }
>
> I'd call this message bloat. ;) This is the first time the assertion
> triggers since it was added.
> You could instead remove the assert(), remove bcm43xx_max_led_err
> and use dprintkl instead of printkl.
>
> > };
> >
> > if (led->activelow)
> > Index: wireless-2.6/drivers/net/wireless/bcm43xx/bcm43xx_leds.h
> > ===================================================================
> > --- wireless-2.6.orig/drivers/net/wireless/bcm43xx/bcm43xx_leds.h
> > +++ wireless-2.6/drivers/net/wireless/bcm43xx/bcm43xx_leds.h
> > @@ -24,6 +24,10 @@ struct bcm43xx_led {
> >
> > #define BCM43xx_LED_BEHAVIOUR 0x7F
> > #define BCM43xx_LED_ACTIVELOW 0x80
> > +#define BCM43xx_LED_BCM4303_0 0x2B
> > +#define BCM43xx_LED_BCM4303_1 0x78
> > +#define BCM43xx_LED_BCM4303_2 0x2E
> > +#define BCM43xx_LED_BCM4303_3 0x19
>
> Add these to the enum below, instead, please.
> The defines above are masks and not the behaviour values.
>
> > enum { /* LED behaviour values */
> > BCM43xx_LED_OFF,
> > BCM43xx_LED_ON,
I took Michael's suggestions before merging your patch...FYI! :-)
John
--
John W. Linville
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org
next prev parent reply other threads:[~2006-11-01 3:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 4:38 [PATCH] bcm43xx: fix unexpected LED control values in BCM4303 sprom Larry Finger
[not found] ` <4535AFC2.mail3S81JGSDJ-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2006-10-18 14:37 ` Michael Buesch
[not found] ` <200610181637.08698.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2006-11-01 3:49 ` John W. Linville [this message]
[not found] ` <20061101034936.GD9309-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2006-11-01 4:34 ` Larry Finger
2006-11-01 11:27 ` Michael Buesch
[not found] ` <454823CC.9070808-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2006-11-01 13:12 ` John W. Linville
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=20061101034936.GD9309@tuxdriver.com \
--to=linville-2xusbdqka4r54taoqtywwq@public.gmane.org \
--cc=Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
--cc=Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org \
--cc=mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=st3-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.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).