Linux EFI development
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Daniel Ferguson <danielf@os.amperecomputing.com>
Cc: Ard Biesheuvel <ardb@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Len Brown <lenb@kernel.org>, "James Morse" <james.morse@arm.com>,
	Tony Luck <tony.luck@intel.com>, "Borislav Petkov" <bp@alien8.de>,
	<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-acpi@vger.kernel.org>, <linux-efi@vger.kernel.org>,
	<linux-edac@vger.kernel.org>,
	Jason Tian <jason@os.amperecomputing.com>,
	Shengwei Luo <luoshengwei@huawei.com>,
	Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Shiju Jose <shiju.jose@huawei.com>
Subject: Re: [PATCH v4 0/5] Fix issues with ARM Processor CPER records
Date: Fri, 8 Aug 2025 16:01:21 +0100	[thread overview]
Message-ID: <20250808160121.000038bd@huawei.com> (raw)
In-Reply-To: <385eca9a-0366-4f3a-95cf-6f19101957ea@os.amperecomputing.com>

On Tue, 5 Aug 2025 11:39:38 -0700
Daniel Ferguson <danielf@os.amperecomputing.com> wrote:

> On 8/5/2025 11:35 AM, Daniel Ferguson wrote:
> > [NO NEED FOR INTERNAL REVIEW, THIS IS JUST A TEST]  
> 
> Yes, PLEASE REVIEW...
> I accidentally left that message in...
> 
> ~Daniel

Hi Daniel,

No problem with you picking this up to take forwards as I gather you asked
Mauro first, but good to mention that change and that it's with agreement
(or not if it's abandoned code which I don't think this was.) 

Thanks,

Jonathan

  reply	other threads:[~2025-08-08 15:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-05 18:35 [PATCH v4 0/5] Fix issues with ARM Processor CPER records Daniel Ferguson
2025-08-05 18:35 ` [PATCH v4 1/5] RAS: Report all ARM processor CPER information to userspace Daniel Ferguson
2025-08-08 15:22   ` Jonathan Cameron
2025-08-09 15:55     ` Mauro Carvalho Chehab
2025-08-11 10:52       ` Jonathan Cameron
2025-08-11 22:37         ` Daniel Ferguson
2025-08-12 14:05           ` Jonathan Cameron
2025-08-05 18:35 ` [PATCH v4 2/5] efi/cper: Adjust infopfx size to accept an extra space Daniel Ferguson
2025-08-05 18:35 ` [PATCH v4 3/5] efi/cper: Add a new helper function to print bitmasks Daniel Ferguson
2025-08-08 15:23   ` Jonathan Cameron
2025-08-05 18:35 ` [PATCH v4 4/5] efi/cper: align ARM CPER type with UEFI 2.9A/2.10 specs Daniel Ferguson
2025-08-05 18:35 ` [PATCH v4 5/5] docs: efi: add CPER functions to driver-api Daniel Ferguson
2025-08-05 18:39 ` [PATCH v4 0/5] Fix issues with ARM Processor CPER records Daniel Ferguson
2025-08-08 15:01   ` Jonathan Cameron [this message]
2025-08-08 19:03     ` Daniel Ferguson
2025-08-09 15:49       ` Mauro Carvalho Chehab

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=20250808160121.000038bd@huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=ardb@kernel.org \
    --cc=bp@alien8.de \
    --cc=corbet@lwn.net \
    --cc=danielf@os.amperecomputing.com \
    --cc=james.morse@arm.com \
    --cc=jason@os.amperecomputing.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luoshengwei@huawei.com \
    --cc=mchehab+huawei@kernel.org \
    --cc=rafael@kernel.org \
    --cc=shiju.jose@huawei.com \
    --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