From: Peng Sun <sironhide0null@gmail.com>
To: liodot@gmail.com, charrer@alacritech.com, gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, Peng Sun <sironhide0null@gmail.com>
Subject: [PATCH 0/2] staging: slicoss: fix sparse warnings
Date: Tue, 13 Sep 2016 04:00:20 -0700 [thread overview]
Message-ID: <cover.1473764379.git.sironhide0null@gmail.com> (raw)
base: next-20160909, commit-id d221eb9f
Peng Sun (2):
staging: slicoss: slic.h: add several macros to fix sparse warnings
staging: slicoss: slicoss.c: fix different address space sparse
warnings
drivers/staging/slicoss/slic.h | 45 +++++++++++++++++++++
drivers/staging/slicoss/slicoss.c | 82 +++++++++++++++++++++++----------------
2 files changed, 94 insertions(+), 33 deletions(-)
--
2.7.4
next reply other threads:[~2016-09-13 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 11:00 Peng Sun [this message]
2016-09-13 11:00 ` [PATCH 1/2] staging: slicoss: slic.h: add several macros to fix sparse warnings Peng Sun
2016-09-13 11:00 ` [PATCH 2/2] staging: slicoss: slicoss.c: fix different address space " Peng Sun
2016-09-13 17:46 ` kbuild test robot
2016-09-13 17:57 ` kbuild test robot
2016-09-13 22:35 ` kbuild test robot
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.1473764379.git.sironhide0null@gmail.com \
--to=sironhide0null@gmail.com \
--cc=charrer@alacritech.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liodot@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