From: Yogesh Ashok Powar <yogeshp@marvell.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Lennert Buytenhek <buytenh@wantstofly.org>,
Nishant Sarmukadam <nishants@marvell.com>
Subject: [PATCH 0/2] mwl8k: Fixing sparse warnings
Date: Thu, 6 Mar 2014 20:42:18 +0530 [thread overview]
Message-ID: <cover.1394107732.git.yogeshp@marvell.com> (raw)
Fixing Sparse warnings.
Yogesh Ashok Powar (2):
mwl8k: le32_to_cpu is redandant on ioread32
mwl8k: mwl8k_update_survey can be static
drivers/net/wireless/mwl8k.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
--
1.8.3.4
next reply other threads:[~2014-03-06 15:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 15:12 Yogesh Ashok Powar [this message]
2014-03-06 15:12 ` [PATCH 1/2] mwl8k: le32_to_cpu cast to restricted Yogesh Ashok Powar
2014-03-06 15:12 ` [PATCH 2/2] mwl8k: mwl8k_update_survey can be static Yogesh Ashok Powar
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=cover.1394107732.git.yogeshp@marvell.com \
--to=yogeshp@marvell.com \
--cc=buytenh@wantstofly.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=nishants@marvell.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).