From: Michael Buesch <mb@bu3sch.de>
To: Mariusz Kozlowski <m.kozlowski@tuxland.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: orinoco driver question
Date: Sat, 4 Nov 2006 22:04:57 +0100 [thread overview]
Message-ID: <200611042204.57560.mb@bu3sch.de> (raw)
In-Reply-To: <200611031613.25483.m.kozlowski@tuxland.pl>
On Friday 03 November 2006 16:13, Mariusz Kozlowski wrote:
> Hi there,
>
> Hope that's not a problem to ask some 'newbie' kernel coding stuff here. Here
> it goes:
>
> There are those two orinoco ioctl's
>
> - orinoco_ioctl_setport3
> - orinoco_ioctl_getport3
>
> Both take 'char *extra' as an argument to set/get 'priv->prefer_port3'. The
> argument value to orinoco_ioctl_setport3 can be either 0 (IEEE ad-hoc mode)
> or 1 (Lucent proprietary ad-hoc mode) the rest is -EINVAL. I don't get why
> there is a need for an extra 'int' variable and casts in the code.
> Using 'char *extra' seems to be fine there. To visualize what I mean here is
> the patch:
>
> --- linux-2.6.19-rc4-orig/drivers/net/wireless/orinoco.c 2006-11-02
> 23:52:39.000000000 +0100
> +++ linux-2.6.19-rc4/drivers/net/wireless/orinoco.c 2006-11-03
> 16:02:45.000000000 +0100
> @@ -3658,14 +3658,13 @@ static int orinoco_ioctl_setport3(struct
> char *extra)
> {
> struct orinoco_private *priv = netdev_priv(dev);
> - int val = *( (int *) extra );
> int err = 0;
> unsigned long flags;
>
> if (orinoco_lock(priv, &flags) != 0)
> return -EBUSY;
>
> - switch (val) {
> + switch (*extra) {
> case 0: /* Try to do IEEE ad-hoc mode */
> if (! priv->has_ibss) {
> err = -EINVAL;
> @@ -3704,9 +3703,8 @@ static int orinoco_ioctl_getport3(struct
> char *extra)
> {
> struct orinoco_private *priv = netdev_priv(dev);
> - int *val = (int *) extra;
>
> - *val = priv->prefer_port3;
> + *extra = (char)priv->prefer_port3;
> return 0;
> }
>
> I don't think this patch decreases code readability. This is just an example
> but if there are more functions like this doesn't removing 'redundant' (?)
> variables make the code better?
This breaks on bigendian systems.
--
Greetings Michael.
prev parent reply other threads:[~2006-11-04 21:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-03 15:13 orinoco driver question Mariusz Kozlowski
2006-11-03 15:32 ` Andreas Schwab
2006-11-03 15:38 ` Mariusz Kozlowski
2006-11-04 21:04 ` 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=200611042204.57560.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=m.kozlowski@tuxland.pl \
/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