From: Abhinav Singh <singhabhinav9051571833@gmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: tony.luck@intel.com, qiuxu.zhuo@intel.com, james.morse@arm.com,
mchehab@kernel.org, rric@kernel.org, linux-edac@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH] driver : edac : Fix warning using plain integer as NULL
Date: Tue, 28 Nov 2023 00:23:54 +0530 [thread overview]
Message-ID: <95fc95c8-dac6-4137-a9cd-29f27da64e41@gmail.com> (raw)
In-Reply-To: <20231127183941.GGZWTibScFM4lgbqkG@fat_crate.local>
On 11/28/23 00:09, Borislav Petkov wrote:
> On Mon, Nov 27, 2023 at 11:53:02PM +0530, Abhinav Singh wrote:
>> Hello, thanks for reviewing this. As of now this is only a warning issue in
>> kernel. I saw this post by linus
>> https://www.spinics.net/lists/linux-sparse/msg10066.html and thought of
>> submitting a patch. Also a similar patch of mine got accepted
>> https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg2560740.html,
>> so thought about opening this one as well.
>
> Lemme try to understand what you're saying: just because someone
> accepted a patch of yours, then others should not ask you to improve
> your commit message so that it explains *why* a change should be done.
>
> How about you put the gist of what Linus is saying in your commit
> message? Don't you think it would be a much better commit message then?
>
> Especially if it explains why, even if it is the case that 0 == NULL, we
> don't want those in the kernel.
>
> Hmmm?
>
Hello, my sincere apologies, I wrongly interpreted that you were asking
for a reason in reply rather than in the commit message itself. Yeah I
agree putting a reason in the commit message will make more sense. Just
to be correct this time, I need to put a reason why this needs to be
fixed, in the patch itself, right?
Thank You,
Abhinav Singh
next prev parent reply other threads:[~2023-11-27 18:54 UTC|newest]
Thread overview: 16+ 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2023-11-09 21:20 [PATCH] driver : edac " 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=95fc95c8-dac6-4137-a9cd-29f27da64e41@gmail.com \
--to=singhabhinav9051571833@gmail.com \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.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