From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Adrian Remonda <adrianremonda@gmail.com>
Cc: devel@driverdev.osuosl.org, christian.gromm@microchip.com,
linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org
Subject: Re: [PATCHv4 2/6] Staging: most: mostcore/core.c. Fix "Using plain integer as NULL pointer" warnings
Date: Tue, 4 Aug 2015 12:21:32 +0530 [thread overview]
Message-ID: <20150804065132.GA7744@sudip-pc> (raw)
In-Reply-To: <1438636959-757-3-git-send-email-adrianremonda@gmail.com>
On Mon, Aug 03, 2015 at 11:22:35PM +0200, Adrian Remonda wrote:
> This patch fixes the warning generated by sparse: "Using plain integer
> as NULL pointer" by replacing the offending 0 with NULL.
>
> Signed-off-by: Adrian Remonda <adrianremonda@gmail.com>
> ---
This patch will not apply because of 7ac5c9f0a022 ("Staging: most: fix
snprintf() is printing too much").
You need to update your tree.
regards
sudip
next prev parent reply other threads:[~2015-08-04 6:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 21:22 [PATCHv4 0/6] Staging: most: several warnings fix reported by sparse Adrian Remonda
2015-08-03 21:22 ` [PATCHv4 1/6] Staging: most: mostcore/core.c. Fix "missing static keyword" warnings Adrian Remonda
2015-08-03 21:22 ` [PATCHv4 2/6] Staging: most: mostcore/core.c. Fix "Using plain integer as NULL pointer" warnings Adrian Remonda
2015-08-04 6:51 ` Sudip Mukherjee [this message]
2015-08-03 21:22 ` [PATCHv4 3/6] Staging: most: hdm-usb/hdm_usb.c. Fix "missing static keyword" warnings Adrian Remonda
2015-08-03 21:22 ` [PATCHv4 4/6] Staging: most: hdm-dim2/dim2_hal.c. Fix "Using plain integer as NULL pointer" warnings Adrian Remonda
2015-08-03 21:22 ` [PATCHv4 5/6] Staging: most: aim-cdev/cdev.c. Fix "missing static keyword" warnings Adrian Remonda
2015-08-03 21:22 ` [PATCHv4 6/6] Staging: most: aim-network/networking.c. Fix "Using plain integer as NULL pointer" warnings Adrian Remonda
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=20150804065132.GA7744@sudip-pc \
--to=sudipm.mukherjee@gmail.com \
--cc=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