From: Christian Lamparter <chunkeey@web.de>
To: "Tomas Winkler" <tomasw@gmail.com>
Cc: linux-wireless@vger.kernel.org,
"John W Linville" <linville@tuxdriver.com>,
"Larry Finger" <Larry.Finger@lwfinger.net>
Subject: Re: [PATCH] p54usb: support LM87 firmwares
Date: Wed, 3 Sep 2008 02:00:50 +0200 [thread overview]
Message-ID: <200809030200.50745.chunkeey@web.de> (raw)
In-Reply-To: <1ba2fa240809021614t4dfb1422sa82efeae8869ff6b@mail.gmail.com>
On Wednesday 03 September 2008 01:14:12 Tomas Winkler wrote:
> > diff -Nurp a/drivers/net/wireless/p54/p54common.c
> > b/drivers/net/wireless/p54/p54common.c ---
> > a/drivers/net/wireless/p54/p54common.c 2008-09-01 22:25:35.000000000
> > +0200 +++ b/drivers/net/wireless/p54/p54common.c 2008-09-02
> > 21:29:47.000000000 +0200 @@ -93,7 +93,10 @@ int p54_parse_firmware(struct
> > ieee80211_
> > u32 code = le32_to_cpu(bootrec->code);
> > switch (code) {
> > case BR_CODE_COMPONENT_ID:
> > - switch (be32_to_cpu(*(__be32 *)bootrec->data)) {
> > + priv->fw_interface =
> > + be32_to_cpu(*(__be32 *)bootrec->data);
>
> what about be32_to_cpup?
> Tomas
whats the main difference between be32_to_cpu vs be32_to_cpus vs be32_to_cpup?
Does the extra p just stand for something like "pointer"?
hmm,
if yes, >>*<<(__be32 *)bootrec->data.
if no, please tell me more about it ;-).
Regards,
Chr
next prev parent reply other threads:[~2008-09-02 23:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 19:39 [PATCH] p54usb: support LM87 firmwares Christian Lamparter
2008-09-02 23:14 ` Tomas Winkler
2008-09-03 0:00 ` Christian Lamparter [this message]
2008-09-04 1:44 ` Pavel Roskin
2008-09-04 10:29 ` [PATCH v2] " Christian Lamparter
2008-09-06 22:57 ` Larry Finger
2008-09-06 23:19 ` Chr
2008-09-06 23:33 ` Larry Finger
2008-09-07 0:25 ` Chr
2008-09-07 0:32 ` Larry Finger
2008-09-07 0:56 ` Christian Lamparter
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=200809030200.50745.chunkeey@web.de \
--to=chunkeey@web.de \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=tomasw@gmail.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 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).