From: "ishii.shuuichir@fujitsu.com" <ishii.shuuichir@fujitsu.com>
To: "'baicar@os.amperecomputing.com'" <baicar@os.amperecomputing.com>
Cc: "'linux-arm-kernel@lists.infradead.org'"
<linux-arm-kernel@lists.infradead.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'linux-acpi@vger.kernel.org'" <linux-acpi@vger.kernel.org>,
"ishii.shuuichir@fujitsu.com" <ishii.shuuichir@fujitsu.com>
Subject: About the ARM Error Source Table Support patch series.
Date: Mon, 18 Oct 2021 06:18:25 +0000 [thread overview]
Message-ID: <TYCPR01MB61604CDECA902F560C805EF4E9BC9@TYCPR01MB6160.jpnprd01.prod.outlook.com> (raw)
Hi Tyler, and everyone.
nice to meet you.
We are trying to develop an AEST driver.
We checked the llinux ML to see if a patch series has already been posted, and found that you have posted an RFC patch series.
[1] https://lore.kernel.org/linux-acpi/1562086280-5351-1-git-send-email-baicar@os.amperecomputing.com/
So We have the following questions.
1) Is it correct to assume that the RFC patch you have already posted is the latest one?
2) In that case, we would like to implement features as needed based on this RFC patch. Is there any problem with that?
Best regards,
Shuuichirou.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: "ishii.shuuichir@fujitsu.com" <ishii.shuuichir@fujitsu.com>
To: "'baicar@os.amperecomputing.com'" <baicar@os.amperecomputing.com>
Cc: "'linux-arm-kernel@lists.infradead.org'"
<linux-arm-kernel@lists.infradead.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'linux-acpi@vger.kernel.org'" <linux-acpi@vger.kernel.org>,
"ishii.shuuichir@fujitsu.com" <ishii.shuuichir@fujitsu.com>
Subject: About the ARM Error Source Table Support patch series.
Date: Mon, 18 Oct 2021 06:18:25 +0000 [thread overview]
Message-ID: <TYCPR01MB61604CDECA902F560C805EF4E9BC9@TYCPR01MB6160.jpnprd01.prod.outlook.com> (raw)
Hi Tyler, and everyone.
nice to meet you.
We are trying to develop an AEST driver.
We checked the llinux ML to see if a patch series has already been posted, and found that you have posted an RFC patch series.
[1] https://lore.kernel.org/linux-acpi/1562086280-5351-1-git-send-email-baicar@os.amperecomputing.com/
So We have the following questions.
1) Is it correct to assume that the RFC patch you have already posted is the latest one?
2) In that case, we would like to implement features as needed based on this RFC patch. Is there any problem with that?
Best regards,
Shuuichirou.
next reply other threads:[~2021-10-18 6:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 6:18 ishii.shuuichir [this message]
2021-10-18 6:18 ` About the ARM Error Source Table Support patch series ishii.shuuichir
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=TYCPR01MB61604CDECA902F560C805EF4E9BC9@TYCPR01MB6160.jpnprd01.prod.outlook.com \
--to=ishii.shuuichir@fujitsu.com \
--cc=baicar@os.amperecomputing.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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 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.