linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Harvey Harrison <harvey.harrison@gmail.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 2/8] b43: remove remaining b43_radio_{read|write}16 from main.c
Date: Sat, 4 Oct 2008 10:47:57 +0200	[thread overview]
Message-ID: <200810041047.58066.mb@bu3sch.de> (raw)
In-Reply-To: <48E6C8A1.1060404@lwfinger.net>

On Saturday 04 October 2008 03:36:33 Larry Finger wrote:
> Harvey Harrison wrote:
> > The 16 is not necessary anymore and is defnined to read/write.
> > 
> > Signed-off-by: Harvey Harrison <harvey.harrison@gmail.com>
> > ---
> >  drivers/net/wireless/b43/main.c |    4 ++--
> >  1 files changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/drivers/net/wireless/b43/main.c b/drivers/net/wireless/b43/main.c
> > index 6df9b65..cc1f4a9 100644
> > --- a/drivers/net/wireless/b43/main.c
> > +++ b/drivers/net/wireless/b43/main.c
> > @@ -789,7 +789,7 @@ void b43_dummy_transmission(struct b43_wldev *dev)
> >  	b43_write16(dev, 0x0502, 0x0030);
> >  
> >  	if (phy->radio_ver == 0x2050 && phy->radio_rev <= 0x5)
> > -		b43_radio_write16(dev, 0x0051, 0x0017);
> > +		b43_radio_write(dev, 0x0051, 0x0017);
> >  	for (i = 0x00; i < max_loop; i++) {
> >  		value = b43_read16(dev, 0x050E);
> >  		if (value & 0x0080)
> > @@ -809,7 +809,7 @@ void b43_dummy_transmission(struct b43_wldev *dev)
> >  		udelay(10);
> >  	}
> >  	if (phy->radio_ver == 0x2050 && phy->radio_rev <= 0x5)
> > -		b43_radio_write16(dev, 0x0051, 0x0037);
> > +		b43_radio_write(dev, 0x0051, 0x0037);
> >  
> >  	write_unlock(&wl->tx_lock);
> >  	spin_unlock_irq(&wl->irq_lock);
> 
> NACK. The two extra characters are absolutely harmless, but they do
> contain useful information. In addition, who knows if a future
> Broadcom device starts using 32-bit read/writes.

Ok, there are valid reasons for it, there are valid reasons against it...

Can we just agree now that we're not going to apply _any_ cleanups to the
PHY code, please? (So I revoke my mail from Sat Oct  4 00:35:35 2008)

Actual bugfixes are welcome, of course.

-- 
Greetings Michael.

      reply	other threads:[~2008-10-04  8:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-03 20:48 [PATCH 2/8] b43: remove remaining b43_radio_{read|write}16 from main.c Harvey Harrison
2008-10-04  1:36 ` Larry Finger
2008-10-04  8:47   ` Michael Buesch [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=200810041047.58066.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=Larry.Finger@lwfinger.net \
    --cc=harvey.harrison@gmail.com \
    --cc=linux-wireless@vger.kernel.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).