public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Hanjun Guo <guohanjun@huawei.com>
To: "Wilczynski, Michal" <michal.wilczynski@intel.com>,
	Jose Marinho <jose.marinho@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Jeremy Linton <Jeremy.Linton@arm.com>,
	James Morse <James.Morse@arm.com>,
	Rob Herring <Rob.Herring@arm.com>, Will Deacon <will@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-doc@vger.kernel.org>, <linux-acpi@vger.kernel.org>,
	Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>
Subject: Re: [PATCH 1/3 v2] Documentation/arm64: Update ARM and arch reference
Date: Tue, 20 Jun 2023 14:51:26 +0800	[thread overview]
Message-ID: <bedea335-c27c-830b-fdf5-75f77f3baf50@huawei.com> (raw)
In-Reply-To: <c05323a8-5cda-5355-b701-e4acdae99f53@intel.com>

On 2023/6/19 20:22, Wilczynski, Michal wrote:
>>   Participation in this group is open to all UEFI members.  Please see
>>   http://www.uefi.org/workinggroup  for details on group membership.
 >
> Not part of this patch, but while at it maybe fix thehttp://www.uefi.org/workinggroup
> that doesn't work - it returns 404.

Thank you. I think it's https://uefi.org/membership now.

Thanks
Hanjun

  reply	other threads:[~2023-06-20  6:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06  9:35 [PATCH 0/3 v2] Update ACPI documentation for Arm systems Jose Marinho
2023-06-06  9:35 ` [PATCH 1/3 v2] Documentation/arm64: Update ARM and arch reference Jose Marinho
2023-06-06 11:50   ` Robin Murphy
2023-06-19 12:22   ` Wilczynski, Michal
2023-06-20  6:51     ` Hanjun Guo [this message]
2023-06-06  9:35 ` [PATCH 2/3 v2] Documentation/arm64: Update references in arm-acpi Jose Marinho
2023-06-06 11:56   ` Robin Murphy
2023-06-06  9:35 ` [PATCH 3/3 v2] Documentation/arm64: Update ACPI tables from BBR Jose Marinho
2023-06-06 13:37 ` [PATCH 0/3 v2] Update ACPI documentation for Arm systems Sudeep Holla
2023-06-06 23:54 ` Jeremy Linton
2023-06-07 11:02 ` Hanjun Guo
2023-06-14 17:18 ` Catalin Marinas

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=bedea335-c27c-830b-fdf5-75f77f3baf50@huawei.com \
    --to=guohanjun@huawei.com \
    --cc=James.Morse@arm.com \
    --cc=Jeremy.Linton@arm.com \
    --cc=Rob.Herring@arm.com \
    --cc=Samer.El-Haj-Mahmoud@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=corbet@lwn.net \
    --cc=jose.marinho@arm.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=michal.wilczynski@intel.com \
    --cc=will@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