From: AdrianRemonda <adrianremonda@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: devel@driverdev.osuosl.org, christian.gromm@microchip.com,
linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org
Subject: Re: [PATCHv3 0/6] Staging: most: several warnings fix reported by sparse
Date: Mon, 3 Aug 2015 22:29:40 +0200 [thread overview]
Message-ID: <20150803202940.GA5784@debian.home> (raw)
In-Reply-To: <20150803083018.GU5180@mwanda>
On Mon, Aug 03, 2015 at 11:30:18AM +0300, Dan Carpenter wrote:
> The subjects still are not unique. Greg said this earlier.
>
> If you want just do it in two patches.
>
> [patch 1] add static
> [patch 2] use NULL instead of zero
>
> regards,
> dan carpenter
>
Yes, sorry. I totally messed it up. I thought Greg was referring just to
the cover letter.
Thanks for the hints
Regards,
Adrian
prev parent reply other threads:[~2015-08-03 20:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 7:40 [PATCHv3 0/6] Staging: most: several warnings fix reported by sparse Adrian Remonda
2015-08-03 7:40 ` [PATCHv3 1/6] Staging: most: Fix "missing static keyword" warnings Adrian Remonda
2015-08-03 7:40 ` [PATCHv3 2/6] Staging: most: Fix "Using plain integer as NULL pointer" warnings Adrian Remonda
2015-08-03 7:40 ` [PATCHv3 3/6] Staging: most: Fix "missing static keyword" warnings Adrian Remonda
2015-08-03 9:36 ` Christian Gromm
2015-08-03 7:40 ` [PATCHv3 4/6] Staging: most: Fix "Using plain integer as NULL pointer" warnings Adrian Remonda
2015-08-03 7:40 ` [PATCHv3 5/6] Staging: most: Fix "missing static keyword" warnings Adrian Remonda
2015-08-03 7:40 ` [PATCHv3 6/6] Staging: most: Fix "Using plain integer as NULL pointer" warnings Adrian Remonda
2015-08-03 8:30 ` [PATCHv3 0/6] Staging: most: several warnings fix reported by sparse Dan Carpenter
2015-08-03 20:29 ` AdrianRemonda [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=20150803202940.GA5784@debian.home \
--to=adrianremonda@gmail.com \
--cc=christian.gromm@microchip.com \
--cc=dan.carpenter@oracle.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 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.