From: Borislav Petkov <bp@alien8.de>
To: Yazen Ghannam <yazen.ghannam@amd.com>
Cc: Tom Rix <trix@redhat.com>,
tony.luck@intel.com, james.morse@arm.com, mchehab@kernel.org,
rric@kernel.org, linux-edac@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] EDAC/amd64: set variable gpu_node_map storage-class-specifier to static
Date: Mon, 19 Jun 2023 13:07:04 +0200 [thread overview]
Message-ID: <20230619110704.GAZJA22FpkwY108vUh@fat_crate.local> (raw)
In-Reply-To: <89a67e4d-cada-ff57-f702-d5579ea8b39c@amd.com>
On Wed, Jun 14, 2023 at 11:21:46AM -0400, Yazen Ghannam wrote:
> Also, would a Fixes tag be appropriate?
No need. I've squashed this with the topmost commit in tip:ras/core
which introduced gpu_node_map in the first place.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2023-06-19 11:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-10 21:09 [PATCH] EDAC/amd64: set variable gpu_node_map storage-class-specifier to static Tom Rix
2023-06-14 15:21 ` Yazen Ghannam
2023-06-19 11:07 ` Borislav Petkov [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=20230619110704.GAZJA22FpkwY108vUh@fat_crate.local \
--to=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=rric@kernel.org \
--cc=tony.luck@intel.com \
--cc=trix@redhat.com \
--cc=yazen.ghannam@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.