From: karthik alapati <mail@karthek.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Lee Jones <lee.jones@linaro.org>,
Jakub Kicinski <kuba@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Johannes Berg <johannes@sipsolutions.net>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] fix sparse warnings
Date: Sun, 21 Feb 2021 21:00:48 +0530 [thread overview]
Message-ID: <cover.1613921277.git.mail@karthek.com> (raw)
the following patches fixes two byte-order issues
and fixes these sparse warnings
drivers/staging//wimax/i2400m/op-rfkill.c:89:25: warning: incorrect type in assignment (different base types)
drivers/staging//wimax/i2400m/op-rfkill.c:89:25: expected restricted __le16 [usertype] length
drivers/staging//wimax/i2400m/op-rfkill.c:89:25: got unsigned long
.
drivers/staging//wimax/i2400m/fw.c:514:27: warning: restricted __le32 degrades to integer
karthik alapati (2):
staging: wimax/i2400m: fix byte-order issue
staging: wimax/i2400m: convert __le32 type to host byte-order
drivers/staging/wimax/i2400m/fw.c | 2 +-
drivers/staging/wimax/i2400m/op-rfkill.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--
2.30.1
next reply other threads:[~2021-02-21 15:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-21 15:30 karthik alapati [this message]
2021-02-21 15:31 ` [PATCH 1/2] staging: wimax/i2400m: fix byte-order issue karthik alapati
2021-02-21 15:31 ` [PATCH 2/2] staging: wimax/i2400m: convert __le32 type to host byte-order karthik alapati
2021-02-24 14:56 ` [PATCH 0/2] fix sparse warnings karthek
2021-02-24 15:06 ` Dan Carpenter
2021-02-24 16:12 ` karthek
-- strict thread matches above, loose matches on Subject: below --
2023-06-09 9:05 [PATCH 0/2] Fix " Ashok Reddy Soma
2023-06-12 6:36 ` Michal Simek
2023-02-21 7:03 Ashok Reddy Soma
2015-10-29 20:41 Ksenija Stanojevic
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.1613921277.git.mail@karthek.com \
--to=mail@karthek.com \
--cc=arnd@arndb.de \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
/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.