From: Borislav Petkov <bp@alien8.de>
To: Yang Li <yang.lee@linux.alibaba.com>
Cc: tony.luck@intel.com, qiuxu.zhuo@intel.com, mchehab@kernel.org,
james.morse@arm.com, rric@kernel.org, linux-edac@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] EDAC: use NULL instead of using plain integer as pointer
Date: Wed, 17 Mar 2021 12:33:37 +0100 [thread overview]
Message-ID: <20210317113337.GA25069@zn.tnic> (raw)
In-Reply-To: <1615967245-35819-1-git-send-email-yang.lee@linux.alibaba.com>
On Wed, Mar 17, 2021 at 03:47:25PM +0800, Yang Li wrote:
> This fixes the following sparse warnings:
> drivers/edac/sb_edac.c:433:10: warning: Using plain integer as NULL
> pointer
> drivers/edac/sb_edac.c:499:10: warning: Using plain integer as NULL
> pointer
> drivers/edac/sb_edac.c:570:10: warning: Using plain integer as NULL
> pointer
> drivers/edac/sb_edac.c:614:10: warning: Using plain integer as NULL
> pointer
> drivers/edac/sb_edac.c:680:10: warning: Using plain integer as NULL
> pointer
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
> ---
> drivers/edac/sb_edac.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/edac/sb_edac.c b/drivers/edac/sb_edac.c
> index 93daa42..a99df55 100644
> --- a/drivers/edac/sb_edac.c
> +++ b/drivers/edac/sb_edac.c
> @@ -433,7 +433,7 @@ struct sbridge_pvt {
>
> static const struct pci_id_table pci_dev_descr_sbridge_table[] = {
> PCI_ID_TABLE_ENTRY(pci_dev_descr_sbridge, ARRAY_SIZE(pci_dev_descr_sbridge), 1, SANDY_BRIDGE),
> - {0,} /* 0 terminated list. */
> + {NULL,} /* 0 terminated list. */
Why does this matter for list terminators?
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2021-03-17 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 7:47 [PATCH] EDAC: use NULL instead of using plain integer as pointer Yang Li
2021-03-17 11:33 ` Borislav Petkov [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=20210317113337.GA25069@zn.tnic \
--to=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=qiuxu.zhuo@intel.com \
--cc=rric@kernel.org \
--cc=tony.luck@intel.com \
--cc=yang.lee@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).