From: Andrew Morton <akpm@linux-foundation.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Adrian Bunk <bunk@kernel.org>,
dhowells@redhat.com, linville@tuxdriver.com, mb@bu3sch.de,
stefano.brivio@polimi.it,
Broadcom Linux <bcm43xx-dev@lists.berlios.de>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: + drivers-net-wireless-b43legacy-dmac-remove-the-switch-in-b43legacy_dma_init.patch added to -mm tree
Date: Wed, 2 Jul 2008 10:16:50 -0700 [thread overview]
Message-ID: <20080702101650.3f579d21.akpm@linux-foundation.org> (raw)
In-Reply-To: <486BB332.6000703@lwfinger.net>
On Wed, 02 Jul 2008 11:56:18 -0500 Larry Finger <Larry.Finger@lwfinger.net> wrote:
> akpm@linux-foundation.org wrote:
> > The patch titled
> > drivers/net/wireless/b43legacy/dma.c: remove the switch in b43legacy_dma_init()
> > has been added to the -mm tree. Its filename is
> > drivers-net-wireless-b43legacy-dmac-remove-the-switch-in-b43legacy_dma_init.patch
> >
> > ------------------------------------------------------
> > Subject: drivers/net/wireless/b43legacy/dma.c: remove the switch in b43legacy_dma_init()
> > From: Adrian Bunk <bunk@stusta.de>
> >
> > The gcc 3.4 fork used to compile the MN10300 port emits unwanted
> > __ucmpdi2() calls for this switch on a 64bit value.
> >
> > Fix it by transforming the switch to equivalent "if ... else if ..."
> > statements.
> >
> > Signed-off-by: Adrian Bunk <bunk@kernel.org>
> > Cc: David Howells <dhowells@redhat.com>
> > Cc: Stefano Brivio <stefano.brivio@polimi.it>
> > Cc: John W. Linville <linville@tuxdriver.com>
> > Cc: Michael Buesch <mb@bu3sch.de>
> > Cc: Larry Finger <Larry.Finger@lwfinger.net>
> > Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> > ---
> >
> > drivers/net/wireless/b43legacy/dma.c | 16 ++++++----------
> > 1 file changed, 6 insertions(+), 10 deletions(-)
> >
> > diff -puN drivers/net/wireless/b43legacy/dma.c~drivers-net-wireless-b43legacy-dmac-remove-the-switch-in-b43legacy_dma_init drivers/net/wireless/b43legacy/dma.c
> > --- a/drivers/net/wireless/b43legacy/dma.c~drivers-net-wireless-b43legacy-dmac-remove-the-switch-in-b43legacy_dma_init
> > +++ a/drivers/net/wireless/b43legacy/dma.c
> > @@ -1027,19 +1027,15 @@ int b43legacy_dma_init(struct b43legacy_
> > enum b43legacy_dmatype type;
> >
> > dmamask = supported_dma_mask(dev);
> > - switch (dmamask) {
> > - default:
> > - B43legacy_WARN_ON(1);
> > - case DMA_30BIT_MASK:
> > +
> > + if (dmamask == DMA_30BIT_MASK)
> > type = B43legacy_DMA_30BIT;
> > - break;
> > - case DMA_32BIT_MASK:
> > + else if (dmamask == DMA_32BIT_MASK)
> > type = B43legacy_DMA_32BIT;
> > - break;
> > - case DMA_64BIT_MASK:
> > + else if (dmamask == DMA_64BIT_MASK)
> > type = B43legacy_DMA_64BIT;
> > - break;
> > - }
> > + else
> > + B43legacy_WARN_ON(1);
> >
> > err = ssb_dma_set_mask(dev->dev, dmamask);
> > if (err) {
> > _
>
> Andrew,
>
> When I received your E-mail, I wondered why there was not a similar
> "fix" for b43. It was then I discovered how much b43 and b43legacy had
> diverged while I wasn't looking. I have no objections to your patch;
> however, I wonder if it might be better to fix b43legacy in the same
> way that b43 was changed. I have prepared and tested such a fix (shown
> below). The only problem with this is that the patch is much more
> intrusive than Adrian's and there may be a problem getting it into
> 2.6.26 before it is released, but then I do not think that you intend to
> send the -mm patch to 2.6.26.
I don't think we need to fix this in 2.6.26 - I doubt if anyone uses
this driver on frv - it's mainly a "make allmodconfig work on FRV"
thing.
next prev parent reply other threads:[~2008-07-02 17:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 8:35 + drivers-net-wireless-b43legacy-dmac-remove-the-switch-in-b43legacy_dma_init.patch added to -mm tree akpm
2008-07-02 16:56 ` Larry Finger
2008-07-02 17:16 ` Andrew Morton [this message]
2008-07-02 21:03 ` Michael Buesch
2008-07-02 21:03 ` Michael Buesch
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=20080702101650.3f579d21.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Larry.Finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=bunk@kernel.org \
--cc=dhowells@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=stefano.brivio@polimi.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.