From: Abhinav Singh <singhabhinav9051571833@gmail.com>
To: mchehab@kernel.org, bp@alien8.de, tony.luck@intel.com,
james.morse@arm.com, rric@kernel.org, qiuxu.zhuo@intel.com
Cc: linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] driver : edac : Fix warning using plain integer as NULL
Date: Tue, 28 Nov 2023 03:17:51 +0530 [thread overview]
Message-ID: <916abed0-23f7-482c-b7a1-c2a081ac2122@gmail.com> (raw)
In-Reply-To: <20231127214156.432669-1-singhabhinav9051571833@gmail.com>
On 11/28/23 03:11, Abhinav Singh wrote:
> Sparse static analysis tools generate a warning with this message
> "Using plain integer as NULL pointer". In this case this warning is
> being shown because we are trying to initialize pointer to NULL using
> integer value 0.
>
> The reason for this change is that use of numeric 0 for a null pointer is
> unacceptable. See this link for the long description why:
> Link: https://www.spinics.net/lists/linux-sparse/msg10066.html
>
> Signed-off-by: Abhinav Singh <singhabhinav9051571833@gmail.com>
> ---
> v1 -> v2: 1. Fixed the comment section descrbing the current code.
> 2. Added a reason for why this change is required.
>
> drivers/edac/i7core_edac.c | 4 ++--
> drivers/edac/sb_edac.c | 6 +++---
> 2 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/edac/i7core_edac.c b/drivers/edac/i7core_edac.c
> index 08bf20c60111..4c76d0f180ec 100644
> --- a/drivers/edac/i7core_edac.c
> +++ b/drivers/edac/i7core_edac.c
> @@ -376,7 +376,7 @@ static const struct pci_id_table pci_dev_table[] = {
> PCI_ID_TABLE_ENTRY(pci_dev_descr_i7core_nehalem),
> PCI_ID_TABLE_ENTRY(pci_dev_descr_lynnfield),
> PCI_ID_TABLE_ENTRY(pci_dev_descr_i7core_westmere),
> - {NULL,} /* 0 terminated list. */
> + {NULL,} /* NULL terminated list. */
> };
>
> /*
> @@ -385,7 +385,7 @@ static const struct pci_id_table pci_dev_table[] = {
> static const struct pci_device_id i7core_pci_tbl[] = {
> {PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_X58_HUB_MGMT)},
> {PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_LYNNFIELD_QPI_LINK0)},
> - {0,} /* 0 terminated list. */
> + {0,} /* NULL terminated list. */
> };
>
> /****************************************************************************
> diff --git a/drivers/edac/sb_edac.c b/drivers/edac/sb_edac.c
> index a3f50a66de33..5d9a2963dc54 100644
> --- a/drivers/edac/sb_edac.c
> +++ b/drivers/edac/sb_edac.c
> @@ -439,7 +439,7 @@ static const struct pci_id_descr pci_dev_descr_sbridge[] = {
>
> 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),
> - {NULL,} /* 0 terminated list. */
> + {NULL,} /* NULL terminated list. */
> };
>
> /* This changes depending if 1HA or 2HA:
> @@ -576,7 +576,7 @@ static const struct pci_id_descr pci_dev_descr_haswell[] = {
>
> static const struct pci_id_table pci_dev_descr_haswell_table[] = {
> PCI_ID_TABLE_ENTRY(pci_dev_descr_haswell, 13, 2, HASWELL),
> - {NULL,} /* 0 terminated list. */
> + {NULL,} /* NULL terminated list. */
> };
>
> /* Knight's Landing Support */
> @@ -686,7 +686,7 @@ static const struct pci_id_descr pci_dev_descr_broadwell[] = {
>
> static const struct pci_id_table pci_dev_descr_broadwell_table[] = {
> PCI_ID_TABLE_ENTRY(pci_dev_descr_broadwell, 10, 2, BROADWELL),
> - {NULL,} /* 0 terminated list. */
> + {NULL,} /* NULL terminated list. */
> };
>
>
Thank You, for explaining me what needs to be done. Yeah without a
proper reason a change is never really clear which can be confusing to
anyone looking. I will make sure I add a reason in every patch from now on.
Thank You,
Abhinav Singh
next prev parent reply other threads:[~2023-11-27 21:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 21:21 [PATCH] driver : edac : Fix warning using plain integer as NULL Abhinav Singh
2023-11-25 19:37 ` Abhinav Singh
2023-11-27 17:14 ` Borislav Petkov
2023-11-27 18:23 ` Abhinav Singh
2023-11-27 18:39 ` Borislav Petkov
2023-11-27 18:53 ` Abhinav Singh
2023-11-27 20:05 ` Borislav Petkov
2023-11-27 20:19 ` Abhinav Singh
2023-11-27 20:29 ` Borislav Petkov
2023-11-27 21:41 ` [PATCH v2] " Abhinav Singh
2023-11-27 21:47 ` Abhinav Singh [this message]
2023-11-28 7:47 ` Zhuo, Qiuxu
2023-11-28 14:17 ` [PATCH v3] " Abhinav Singh
2023-11-28 14:43 ` Borislav Petkov
2023-11-28 15:06 ` Abhinav Singh
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=916abed0-23f7-482c-b7a1-c2a081ac2122@gmail.com \
--to=singhabhinav9051571833@gmail.com \
--cc=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 \
/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