From: simran singhal <singhalsimran0@gmail.com>
To: Larry.Finger@lwfinger.net
Cc: florian.c.schilhabel@googlemail.com, gregkh@linuxfoundation.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
oleg.drokin@intel.com, marvin24@gmx.de,
outreachy-kernel@googlegroups.com
Subject: [PATCH v5 0/5] Remove unnecessary cast on void pointer
Date: Sat, 4 Mar 2017 21:00:48 +0530 [thread overview]
Message-ID: <1488641453-22575-1-git-send-email-singhalsimran0@gmail.com> (raw)
This patch-series removes unnecessary cast on void pointer in various
drivers.
v5:
-Fixed compliation warning in lustre/lustre/llite/range_lock.c
which remain unfixed in v3.
v4:
-change the cover-letter subject
v3:
-Fixed compilation warning in lustre/lustre/llite/range_lock.c
simran singhal (5):
staging: nvec: Remove unnecessary cast on void pointer
staging: lustre: Remove unnecessary cast on void pointer
staging: lustre: lustre: Remove unnecessary cast on void pointer
staging: rts5208: Remove unnecessary cast on void pointer
staging: rtl8712: Remove unnecessary cast on void pointer
drivers/staging/lustre/lustre/llite/range_lock.c | 2 +-
drivers/staging/lustre/lustre/lmv/lmv_obd.c | 4 ++--
drivers/staging/nvec/nvec_kbd.c | 2 +-
drivers/staging/rtl8712/rtl8712_recv.c | 11 +++++------
drivers/staging/rts5208/rtsx_transport.c | 3 +--
5 files changed, 10 insertions(+), 12 deletions(-)
--
2.7.4
next reply other threads:[~2017-03-04 15:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-04 15:30 simran singhal [this message]
2017-03-04 15:30 ` [PATCH v5 1/5] staging: nvec: " simran singhal
2017-03-04 15:30 ` [PATCH v5 2/5] staging: lustre: " simran singhal
2017-03-05 0:51 ` James Simmons
2017-03-04 15:30 ` [PATCH v5 3/5] staging: lustre: " simran singhal
2017-03-05 0:51 ` James Simmons
2017-03-04 15:30 ` [PATCH v5 4/5] staging: rts5208: " simran singhal
2017-03-04 15:30 ` [PATCH v5 5/5] staging: rtl8712: " simran singhal
2017-03-04 15:43 ` [Outreachy kernel] [PATCH v5 0/5] " Julia Lawall
2017-03-04 15:52 ` Joe Perches
2017-03-04 16:03 ` SIMRAN SINGHAL
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=1488641453-22575-1-git-send-email-singhalsimran0@gmail.com \
--to=singhalsimran0@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=devel@driverdev.osuosl.org \
--cc=florian.c.schilhabel@googlemail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marvin24@gmx.de \
--cc=oleg.drokin@intel.com \
--cc=outreachy-kernel@googlegroups.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
all inboxes | Powered by JetHome®