From: Yazen Ghannam <yazen.ghannam@amd.com>
To: "Jiri Slaby (SUSE)" <jirislaby@kernel.org>, bp@alien8.de
Cc: yazen.ghannam@amd.com, linux-kernel@vger.kernel.org,
Tony Luck <tony.luck@intel.com>,
James Morse <james.morse@arm.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Robert Richter <rric@kernel.org>,
linux-edac@vger.kernel.org
Subject: Re: [PATCH 1/7] EDAC/amd64: Remove amd64_pvt::ext_nbcfg
Date: Wed, 14 Feb 2024 15:23:11 -0500 [thread overview]
Message-ID: <fc83e824-f37e-4164-95b3-e57bee60b2a9@amd.com> (raw)
In-Reply-To: <20240213112051.27715-2-jirislaby@kernel.org>
On 2/13/2024 6:20 AM, Jiri Slaby (SUSE) wrote:
> Commit cfe40fdb4a46 (amd64_edac: add driver header) added amd64_pvt
> struct with ext_nbcfg in it. But noone used that member since then.
>
> Therefore, remove it.
>
> Found by https://github.com/jirislaby/clang-struct.
>
> Signed-off-by: Jiri Slaby (SUSE) <jirislaby@kernel.org>
> Cc: Yazen Ghannam <yazen.ghannam@amd.com>
> Cc: Borislav Petkov <bp@alien8.de>
> Cc: Tony Luck <tony.luck@intel.com>
> Cc: James Morse <james.morse@arm.com>
> Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
> Cc: Robert Richter <rric@kernel.org>
> Cc: linux-edac@vger.kernel.org
> ---
> drivers/edac/amd64_edac.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/edac/amd64_edac.h b/drivers/edac/amd64_edac.h
> index 1665f7932bac..b879b12971e7 100644
> --- a/drivers/edac/amd64_edac.h
> +++ b/drivers/edac/amd64_edac.h
> @@ -345,7 +345,6 @@ struct amd64_pvt {
> u32 dchr1; /* DRAM Configuration High DCT1 reg */
> u32 nbcap; /* North Bridge Capabilities */
> u32 nbcfg; /* F10 North Bridge Configuration */
> - u32 ext_nbcfg; /* Extended F10 North Bridge Configuration */
> u32 dhar; /* DRAM Hoist reg */
> u32 dbam0; /* DRAM Base Address Mapping reg for DCT0 */
> u32 dbam1; /* DRAM Base Address Mapping reg for DCT1 */
This field likely was intended to be used with the EXT_NB_MCA_CFG definition.
But I agree it's not used and can be removed.
Reviewed-by: Yazen Ghannam <yazen.ghannam@amd.com>
Thanks,
Yazen
next prev parent reply other threads:[~2024-02-14 20:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 11:20 [PATCH 0/7] EDAC: remove unused structure members Jiri Slaby (SUSE)
2024-02-13 11:20 ` [PATCH 1/7] EDAC/amd64: Remove amd64_pvt::ext_nbcfg Jiri Slaby (SUSE)
2024-02-14 20:23 ` Yazen Ghannam [this message]
2024-02-13 11:20 ` [PATCH 2/7] EDAC/device: Remove edac_dev_sysfs_block_attribute::{block,value} Jiri Slaby (SUSE)
2024-02-13 11:20 ` [PATCH 3/7] EDAC/device: Remove edac_dev_sysfs_block_attribute::store() Jiri Slaby (SUSE)
2024-02-13 11:20 ` [PATCH 4/7] EDAC: Remove dynamic attributes from edac_device_alloc_ctl_info() Jiri Slaby (SUSE)
2024-02-13 11:20 ` [PATCH 5/7] EDAC: Remove edac_pci_ctl_info::edac_subsys Jiri Slaby (SUSE)
2024-02-13 11:20 ` [PATCH 6/7] EDAC: Remove edac_pci_ctl_info::complete Jiri Slaby (SUSE)
2024-02-13 11:20 ` [PATCH 7/7] EDAC: Remove edac_device_ctl_info::removal_complete Jiri Slaby (SUSE)
2024-03-08 9:01 ` [PATCH 0/7] EDAC: remove unused structure members Jiri Slaby
2024-03-08 9:16 ` Borislav Petkov
2024-03-27 17:32 ` Borislav Petkov
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=fc83e824-f37e-4164-95b3-e57bee60b2a9@amd.com \
--to=yazen.ghannam@amd.com \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=jirislaby@kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--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
all inboxes | Powered by JetHome®