From: Markus Elfring <Markus.Elfring@web.de>
To: Karan Sanghavi <karansanghvi98@gmail.com>,
linux-edac@vger.kernel.org, Borislav Petkov <bp@alien8.de>,
Tony Luck <tony.luck@intel.com>,
Yazen Ghannam <Yazen.Ghannam@amd.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2] RAS/AMD/ATL: Fix unintended sign extension issue from coverity
Date: Sun, 24 Nov 2024 10:20:53 +0100 [thread overview]
Message-ID: <9c8cbd29-1ce3-4716-8e13-e13b1e6cdab4@web.de> (raw)
In-Reply-To: <20241108-coverity1593397signextension-v2-1-4acdf3968d2d@gmail.com>
…
> Following the code styleof the file, assigning the u16
> value to u32 variable and using it for the bit wise
> operation, thus ensuring no unintentional sign
> extension occurs.
Would you like to reconsider such a word wrapping approach
besides typo avoidance?
See also:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.12#n94
Regards,
Markus
prev parent reply other threads:[~2024-11-24 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 16:40 Karan Sanghavi
2024-11-12 15:04 ` Yazen Ghannam
2024-11-24 8:45 ` Karan Sanghavi
2024-11-24 9:20 ` Markus Elfring [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=9c8cbd29-1ce3-4716-8e13-e13b1e6cdab4@web.de \
--to=markus.elfring@web.de \
--cc=Yazen.Ghannam@amd.com \
--cc=bp@alien8.de \
--cc=karansanghvi98@gmail.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®