All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH] b43: Eliminate compilation warning in b43_op_set_key
Date: Wed, 14 Jan 2009 17:57:05 +0100	[thread overview]
Message-ID: <200901141757.05441.mb@bu3sch.de> (raw)
In-Reply-To: <496E08FD.9030803@lwfinger.net>

On Wednesday 14 January 2009 16:47:09 Larry Finger wrote:
> John W. Linville wrote:
> > On Tue, Jan 13, 2009 at 06:20:25PM -0600, Larry Finger wrote:
> >> A recent pull from wireless testing generates the following warnin=
g:
> >> =20
> >>    CC [M]  drivers/net/wireless/b43/main.o
> >>  drivers/net/wireless/b43/main.c: In function =E2=80=98b43_op_set_=
key=E2=80=99:
> >>  drivers/net/wireless/b43/main.c:3636: warning: pointer type misma=
tch
> >>  in conditional expression
> >>
> >> This fix was suggested by Johannes Berg <johannes@sipsolutions.net=
>.
> >>
> >> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
> >> ---
> >>
> >> Index: wireless-testing/drivers/net/wireless/b43/main.c
> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >> --- wireless-testing.orig/drivers/net/wireless/b43/main.c
> >> +++ wireless-testing/drivers/net/wireless/b43/main.c
> >> @@ -3630,10 +3630,12 @@ static int b43_op_set_key(struct ieee802
> >> =20
> >>  out_unlock:
> >>  	if (!err) {
> >> +		u8 bcast[ETH_ALEN];
> >> +		memset(bcast, 0xff, ETH_ALEN);
> >=20
> > Isn't there a statically-allocated array w/ the broadcast MAC in it
> > somewhere already?
> >=20
>=20
> Not that I could find.
>=20
> There are several places in mac80211 where the broadcast MAC is
> created on the fly. None of them would benefit from having a static
> array - one would just substitute memcpy for memset and possibly tras=
h
> the cache.
>=20
> There is an array broadcast[MAX_ADDR_LEN] in struct net_device, but i=
t
> would need to be initialized with 0xFF's before usage.
>=20
> I still think that b43 needs to create this array, and that the best
> place to do it is in the error path that is unlikely to be executed.

This is not an error path.
Why don't you simply define
	static const u8 bcast_addr[] =3D { 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF,=
 };
It has zero runtime overhead and is much easier to understand.
And the linker will merge the arrays, if there are multiple of these ar=
rays
in the compilation unit.

Note that you might need to wrap this into
#if B43_DEBUG
#endif
to avoid a compilation warning on non-debug builds in any case

--=20
Greetings, Michael.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2009-01-14 16:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14  0:20 [PATCH] b43: Eliminate compilation warning in b43_op_set_key Larry Finger
2009-01-14 13:34 ` John W. Linville
2009-01-14 15:47   ` Larry Finger
2009-01-14 16:57     ` 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=200901141757.05441.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=Larry.Finger@lwfinger.net \
    --cc=johannes@sipsolutions.net \
    --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 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.