diff for duplicates of <5A85C97C.5080605@arm.com> diff --git a/a/1.txt b/N1/1.txt index 3dea4f4..35416ef 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -60,7 +60,7 @@ Yes, this is my suggestion of what to do if you can't deliver an SError: store the RAS error in the BERT and 'reboot'. -> I CC "liu jun" <liujun88(a)hisilicon.com> who is our UEFI firmware Architect, +> I CC "liu jun" <liujun88@hisilicon.com> who is our UEFI firmware Architect, > if you have firmware requirements, you can raise again. (UEFI? I didn't think there was any of that at EL3, but I'm not familiar with diff --git a/a/content_digest b/N1/content_digest index fe536d3..bdaa9da 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,8 +1,24 @@ - "From\0James Morse <james.morse at arm.com>\0" - "Subject\0Re: [Devel] [PATCH v9 3/7] acpi: apei: Add SEI notification type support for ARMv8\0" + "ref\00184EA26B2509940AA629AE1405DD7F201AC71DE@DGGEMA503-MBS.china.huawei.com\0" + "From\0James Morse <james.morse@arm.com>\0" + "Subject\0Re: [PATCH v9 3/7] acpi: apei: Add SEI notification type support for ARMv8\0" "Date\0Thu, 15 Feb 2018 17:55:08 +0000\0" - "To\0devel@acpica.org\0" - "\01:1\0" + "To\0gengdongjiu <gengdongjiu@huawei.com>\0" + "Cc\0christoffer.dall@linaro.org <christoffer.dall@linaro.org>" + marc.zyngier@arm.com <marc.zyngier@arm.com> + linux@armlinux.org.uk <linux@armlinux.org.uk> + catalin.marinas@arm.com <catalin.marinas@arm.com> + rjw@rjwysocki.net <rjw@rjwysocki.net> + bp@alien8.de <bp@alien8.de> + robert.moore@intel.com <robert.moore@intel.com> + lv.zheng@intel.com <lv.zheng@intel.com> + corbet@lwn.net <corbet@lwn.net> + will.deacon@arm.com <will.deacon@arm.com> + linux-doc@vger.kernel.org <linux-doc@vger.kernel.org> + linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org> + linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org> + kvmarm@lists.cs.columbia.edu <kvmarm@lists.cs.columbia.edu> + " linux-acpi@vger.kernel.org <linux-acpi@vger.kernel.org>\0" + "\00:1\0" "b\0" "Hi gengdongjiu, liu jun\n" "\n" @@ -66,7 +82,7 @@ "the RAS error in the BERT and 'reboot'.\n" "\n" "\n" - "> I CC \"liu jun\" <liujun88(a)hisilicon.com> who is our UEFI firmware Architect,\n" + "> I CC \"liu jun\" <liujun88@hisilicon.com> who is our UEFI firmware Architect,\n" "> if you have firmware requirements, you can raise again.\n" "\n" "(UEFI? I didn't think there was any of that at EL3, but I'm not familiar with\n" @@ -91,4 +107,4 @@ "\n" James -5090de6b3bf32cc2aca241d4116c4e55bd0c2f0c9e7377c03d614d3ec1376f52 +238dfce4677f9ab3bd8dc1f3f16726e39b98745251c70427022e5604af73adb4
diff --git a/a/1.txt b/N2/1.txt index 3dea4f4..35416ef 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -60,7 +60,7 @@ Yes, this is my suggestion of what to do if you can't deliver an SError: store the RAS error in the BERT and 'reboot'. -> I CC "liu jun" <liujun88(a)hisilicon.com> who is our UEFI firmware Architect, +> I CC "liu jun" <liujun88@hisilicon.com> who is our UEFI firmware Architect, > if you have firmware requirements, you can raise again. (UEFI? I didn't think there was any of that at EL3, but I'm not familiar with diff --git a/a/content_digest b/N2/content_digest index fe536d3..02b3ce5 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -1,8 +1,9 @@ - "From\0James Morse <james.morse at arm.com>\0" - "Subject\0Re: [Devel] [PATCH v9 3/7] acpi: apei: Add SEI notification type support for ARMv8\0" + "ref\00184EA26B2509940AA629AE1405DD7F201AC71DE@DGGEMA503-MBS.china.huawei.com\0" + "From\0james.morse@arm.com (James Morse)\0" + "Subject\0[PATCH v9 3/7] acpi: apei: Add SEI notification type support for ARMv8\0" "Date\0Thu, 15 Feb 2018 17:55:08 +0000\0" - "To\0devel@acpica.org\0" - "\01:1\0" + "To\0linux-arm-kernel@lists.infradead.org\0" + "\00:1\0" "b\0" "Hi gengdongjiu, liu jun\n" "\n" @@ -66,7 +67,7 @@ "the RAS error in the BERT and 'reboot'.\n" "\n" "\n" - "> I CC \"liu jun\" <liujun88(a)hisilicon.com> who is our UEFI firmware Architect,\n" + "> I CC \"liu jun\" <liujun88@hisilicon.com> who is our UEFI firmware Architect,\n" "> if you have firmware requirements, you can raise again.\n" "\n" "(UEFI? I didn't think there was any of that at EL3, but I'm not familiar with\n" @@ -91,4 +92,4 @@ "\n" James -5090de6b3bf32cc2aca241d4116c4e55bd0c2f0c9e7377c03d614d3ec1376f52 +5986a7518cb8d85b8669e63dc80fe41fa7d6d897902eb79105496d24cc462651
diff --git a/a/1.txt b/N3/1.txt index 3dea4f4..35416ef 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -60,7 +60,7 @@ Yes, this is my suggestion of what to do if you can't deliver an SError: store the RAS error in the BERT and 'reboot'. -> I CC "liu jun" <liujun88(a)hisilicon.com> who is our UEFI firmware Architect, +> I CC "liu jun" <liujun88@hisilicon.com> who is our UEFI firmware Architect, > if you have firmware requirements, you can raise again. (UEFI? I didn't think there was any of that at EL3, but I'm not familiar with diff --git a/a/content_digest b/N3/content_digest index fe536d3..d713a9b 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -1,8 +1,27 @@ - "From\0James Morse <james.morse at arm.com>\0" - "Subject\0Re: [Devel] [PATCH v9 3/7] acpi: apei: Add SEI notification type support for ARMv8\0" + "ref\00184EA26B2509940AA629AE1405DD7F201AC71DE@DGGEMA503-MBS.china.huawei.com\0" + "From\0James Morse <james.morse@arm.com>\0" + "Subject\0Re: [PATCH v9 3/7] acpi: apei: Add SEI notification type support for ARMv8\0" "Date\0Thu, 15 Feb 2018 17:55:08 +0000\0" - "To\0devel@acpica.org\0" - "\01:1\0" + "To\0gengdongjiu <gengdongjiu@huawei.com>\0" + "Cc\0christoffer.dall@linaro.org <christoffer.dall@linaro.org>" + marc.zyngier@arm.com <marc.zyngier@arm.com> + linux@armlinux.org.uk <linux@armlinux.org.uk> + catalin.marinas@arm.com <catalin.marinas@arm.com> + rjw@rjwysocki.net <rjw@rjwysocki.net> + bp@alien8.de <bp@alien8.de> + robert.moore@intel.com <robert.moore@intel.com> + lv.zheng@intel.com <lv.zheng@intel.com> + corbet@lwn.net <corbet@lwn.net> + will.deacon@arm.com <will.deacon@arm.com> + linux-doc@vger.kernel.org <linux-doc@vger.kernel.org> + linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org> + linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org> + kvmarm@lists.cs.columbia.edu <kvmarm@lists.cs.columbia.edu> + linux-acpi@vger.kernel.org <linux-acpi@vger.kernel.org> + devel@acpica.org <devel@acpica.org> + Huangshaoyu <huangshaoyu@huawei.com> + " Liujun (Jun Liu) <liujun88@hisilicon.com>\0" + "\00:1\0" "b\0" "Hi gengdongjiu, liu jun\n" "\n" @@ -66,7 +85,7 @@ "the RAS error in the BERT and 'reboot'.\n" "\n" "\n" - "> I CC \"liu jun\" <liujun88(a)hisilicon.com> who is our UEFI firmware Architect,\n" + "> I CC \"liu jun\" <liujun88@hisilicon.com> who is our UEFI firmware Architect,\n" "> if you have firmware requirements, you can raise again.\n" "\n" "(UEFI? I didn't think there was any of that at EL3, but I'm not familiar with\n" @@ -91,4 +110,4 @@ "\n" James -5090de6b3bf32cc2aca241d4116c4e55bd0c2f0c9e7377c03d614d3ec1376f52 +9db1688d4ed644bb60e768390769491ada18d2a14c8e86c70892d9ad36b9f203
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.