From: "John W. Linville" <linville@tuxdriver.com>
To: Rami Rosen <roszenrami@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Johannes Berg <johannes@sipsolutions.net>,
buytenh@marvell.com
Subject: Re: [PATCH ] [RESEND] mwl8: fix build warning.
Date: Tue, 21 Apr 2009 16:32:53 -0400 [thread overview]
Message-ID: <20090421203253.GM3369@tuxdriver.com> (raw)
In-Reply-To: <b25312890904210622v3b84eb45pdef0cb3bce253ba0@mail.gmail.com>
On Tue, Apr 21, 2009 at 04:22:01PM +0300, Rami Rosen wrote:
> This patch fixes a build warning in mwl8.c.
> (Marvell TOPDOG wireless driver)
>
> The warning it fixes is: "large integer implicitly truncated to unsigned type."
>
> The rx_ctrl member of the mwl8k_rx_desc struct is 8 bit (__u8 ), whereas trying
> to assign it a 32 bit value (which is returned from cpu_to_le32())
> causes the compiler to issue
> a truncation warning.
>
>
> Signed-off-by: Rami Rosen <ramirose@gmail.com>
>
> --
> (wireless-next)
>
> diff --git a/drivers/net/wireless/mwl8k.c b/drivers/net/wireless/mwl8k.c
> index 57a0268..8bc016c 100644
> --- a/drivers/net/wireless/mwl8k.c
> +++ b/drivers/net/wireless/mwl8k.c
> @@ -893,8 +893,7 @@ static int mwl8k_rxq_init(struct ieee80211_hw *hw,
> int index)
> rx_desc->next_rx_desc_phys_addr =
> cpu_to_le32(rxq->rx_desc_dma
> + nexti * sizeof(*rx_desc));
> - rx_desc->rx_ctrl =
> - cpu_to_le32(MWL8K_RX_CTRL_OWNED_BY_HOST);
> + rx_desc->rx_ctrl = MWL8K_RX_CTRL_OWNED_BY_HOST;
> }
>
> return 0;
This patch is whitspace damaged. I manually recreated it since it
is so simple, but please do be more careful with future patches.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2009-04-21 20:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 13:22 [PATCH ] [RESEND] mwl8: fix build warning Rami Rosen
2009-04-21 13:57 ` John W. Linville
2009-04-21 20:32 ` John W. Linville [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=20090421203253.GM3369@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=buytenh@marvell.com \
--cc=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=roszenrami@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).