From: "Luck, Tony" <tony.luck@intel.com>
To: "Weiny, Ira" <ira.weiny@intel.com>,
"Jiang, Dave" <dave.jiang@intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: "linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] cxl/cper: Remove duplicated GUID defines
Date: Thu, 2 May 2024 19:33:00 +0000 [thread overview]
Message-ID: <SJ1PR11MB6083FB892A28C7872476C26AFC182@SJ1PR11MB6083.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20240502-cper-fix-dup-guid-v1-1-283cc447c7bf@intel.com>
> No fixes tag because the change is only in linux-next.
Do you expect that other commit to be backported to stable/LTS kernels?
If so, a Fixes: tag would help tools find this one to pull along too.
> Tony can I get a quick ack? I think this should go through the CXL tree
> and picked up by Dave.
Sure ... deleting duplicates. Seems good to me.
Acked-by: Tony Luck <tony.luck@intel.com>
-Tony
prev parent reply other threads:[~2024-05-02 19:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 18:42 [PATCH] cxl/cper: Remove duplicated GUID defines Ira Weiny
2024-05-02 19:33 ` 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=SJ1PR11MB6083FB892A28C7872476C26AFC182@SJ1PR11MB6083.namprd11.prod.outlook.com \
--to=tony.luck@intel.com \
--cc=dave.jiang@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).