lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <TYCPR01MB61604CDECA902F560C805EF4E9BC9@TYCPR01MB6160.jpnprd01.prod.outlook.com>
Date:   Mon, 18 Oct 2021 06:18:25 +0000
From:   "ishii.shuuichir@...itsu.com" <ishii.shuuichir@...itsu.com>
To:     "'baicar@...amperecomputing.com'" <baicar@...amperecomputing.com>
CC:     "'linux-arm-kernel@...ts.infradead.org'" 
        <linux-arm-kernel@...ts.infradead.org>,
        "'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>,
        "'linux-acpi@...r.kernel.org'" <linux-acpi@...r.kernel.org>,
        "ishii.shuuichir@...itsu.com" <ishii.shuuichir@...itsu.com>
Subject: About the ARM Error Source Table Support patch series.


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.


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ