From: Greg KH <gregkh@linuxfoundation.org>
To: Adrian Remonda <adrianremonda@gmail.com>
Cc: devel@driverdev.osuosl.org, christian.gromm@microchip.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 0/6] Staging: most: several warnings fix reported by sparse
Date: Sun, 2 Aug 2015 14:10:00 -0700 [thread overview]
Message-ID: <20150802211000.GA14662@kroah.com> (raw)
In-Reply-To: <1438545748-30409-1-git-send-email-adrianremonda@gmail.com>
On Sun, Aug 02, 2015 at 10:02:22PM +0200, Adrian Remonda wrote:
> 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"
You used the same subject for half of these, please be more "unique".
prev parent reply other threads:[~2015-08-02 21:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-02 20:02 Adrian Remonda
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 ` Greg KH [this message]
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=20150802211000.GA14662@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=adrianremonda@gmail.com \
--cc=christian.gromm@microchip.com \
--cc=devel@driverdev.osuosl.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
all inboxes | Powered by JetHome®