From: Adrian Remonda <adrianremonda@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: adrianremonda@gmail.com, gregkh@linuxfoundation.org,
christian.gromm@microchip.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: [PATCHv2 0/6] Staging: most: several warnings fix reported by sparse
Date: Sun, 2 Aug 2015 22:02:22 +0200 [thread overview]
Message-ID: <1438545748-30409-1-git-send-email-adrianremonda@gmail.com> (raw)
This patch series fix several warnings reported by the Sparse tool
Adrian Remonda (6):
Staging: most: static keyword missing
Staging: most: Fix sparse warning "Using plain integer as NULL
pointer"
Staging: most: static keyword missing
Staging: most: Fix sparse warning "Using plain integer as NULL
pointer"
Staging: most: static keyword missing
Staging: most: Fix sparse warning "Using plain integer as NULL
pointer"
drivers/staging/most/aim-cdev/cdev.c | 14 +++++++-------
drivers/staging/most/aim-network/networking.c | 4 ++--
drivers/staging/most/hdm-dim2/dim2_hal.c | 2 +-
drivers/staging/most/hdm-usb/hdm_usb.c | 14 +++++++-------
drivers/staging/most/mostcore/core.c | 16 ++++++++--------
5 files changed, 25 insertions(+), 25 deletions(-)
--
2.1.4
next reply other threads:[~2015-08-02 20:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-02 20:02 Adrian Remonda [this message]
2015-08-02 20:02 ` [PATCHv2 1/6] Staging: most: static keyword missing Adrian Remonda
2015-08-02 20:02 ` [PATCHv2 2/6] Staging: most: Fix sparse warning "Using plain integer as NULL pointer" Adrian Remonda
2015-08-02 20:02 ` [PATCHv2 3/6] Staging: most: static keyword missing Adrian Remonda
2015-08-02 20:02 ` [PATCHv2 4/6] Staging: most: Fix sparse warning "Using plain integer as NULL pointer" Adrian Remonda
2015-08-02 20:02 ` [PATCHv2 5/6] Staging: most: static keyword missing Adrian Remonda
2015-08-02 20:02 ` [PATCHv2 6/6] Staging: most: Fix sparse warning "Using plain integer as NULL pointer" Adrian Remonda
2015-08-02 21:10 ` [PATCHv2 0/6] Staging: most: several warnings fix reported by sparse Greg KH
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=1438545748-30409-1-git-send-email-adrianremonda@gmail.com \
--to=adrianremonda@gmail.com \
--cc=christian.gromm@microchip.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.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 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).