Linux-EDAC Archive mirror
 help / color / mirror / Atom feed
From: Abhinav Singh <singhabhinav9051571833@gmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: mchehab@kernel.org, tony.luck@intel.com, james.morse@arm.com,
	rric@kernel.org, qiuxu.zhuo@intel.com,
	linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] driver : edac : Fix warning using plain integer as NULL
Date: Tue, 28 Nov 2023 20:36:57 +0530	[thread overview]
Message-ID: <83e432ec-b31c-4f90-a87c-8db8983a9d5e@gmail.com> (raw)
In-Reply-To: <20231128144320.GCZWX8iMRIIX6qDyVO@fat_crate.local>

On 11/28/23 20:13, Borislav Petkov wrote:
> On Tue, Nov 28, 2023 at 07:47:03PM +0530, 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.
> 
> Applied after massaging, thanks.
> 
Thanks a lot for reviewing and merging the patch maintainers.

Thank You,
Abhinav Singh

      reply	other threads:[~2023-11-28 15:07 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
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 [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=83e432ec-b31c-4f90-a87c-8db8983a9d5e@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).