public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: Jason Baron <jbaron@akamai.com>
Cc: "Zhuo, Qiuxu" <qiuxu.zhuo@intel.com>,
	Arnd Bergmann <arnd@kernel.org>, Borislav Petkov <bp@alien8.de>,
	Arnd Bergmann <arnd@arndb.de>, James Morse <james.morse@arm.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Robert Richter <rric@kernel.org>, James Ye <jye836@gmail.com>,
	"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] EDAC/ie31200: work around false positive build warning
Date: Thu, 20 Feb 2025 17:13:17 -0800	[thread overview]
Message-ID: <Z7fTLWH5G_UgVZIQ@agluck-desk3> (raw)
In-Reply-To: <5a6ad008-61c6-4f65-82b3-a4e538cbb9e8@akamai.com>

> > It looks like gcc-14 isn't smart enough to recognize that this is a false positive build warning :-).
> > Actually, the dim_info[][] array is always initialized by populate_dimm_info().
> > 
> > > see why the compiler gets confused by the two loops.
> > > 
> > > Instead, rework the two nested loops to only read the addr_decode registers
> > > and then keep only one instance of the dimm info structure.
> > > 
> > > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> 
> Seems fine with the comment adjustment.
> 
> Thanks.
> 
> Acked-by: Jason Baron <jbaron@akamai.com>

Applied (with comment adjustment) to RAS tree edac-drivers branch

Thanks

-Tony

      reply	other threads:[~2025-02-21  1:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-22  6:50 [PATCH] EDAC/ie31200: work around false positive build warning Arnd Bergmann
2025-01-22 14:18 ` Zhuo, Qiuxu
2025-01-24 19:27   ` Jason Baron
2025-02-21  1:13     ` Luck, Tony [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=Z7fTLWH5G_UgVZIQ@agluck-desk3 \
    --to=tony.luck@intel.com \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=bp@alien8.de \
    --cc=james.morse@arm.com \
    --cc=jbaron@akamai.com \
    --cc=jye836@gmail.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 \
    /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