From: "andriy.shevchenko@linux.intel.com" <andriy.shevchenko@linux.intel.com>
To: Shiju Jose <shiju.jose@huawei.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"bp@alien8.de" <bp@alien8.de>,
"james.morse@arm.com" <james.morse@arm.com>,
"lenb@kernel.org" <lenb@kernel.org>,
"tony.luck@intel.com" <tony.luck@intel.com>,
"dan.carpenter@oracle.com" <dan.carpenter@oracle.com>,
"zhangliguang@linux.alibaba.com" <zhangliguang@linux.alibaba.com>,
"Wangkefeng (OS Kernel Lab)" <wangkefeng.wang@huawei.com>,
"jroedel@suse.de" <jroedel@suse.de>,
Linuxarm <linuxarm@huawei.com>,
yangyicong <yangyicong@huawei.com>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
tanxiaofei <tanxiaofei@huawei.com>
Subject: Re: [PATCH v13 0/2] ACPI / APEI: Add support to notify the vendor specific HW errors
Date: Fri, 24 Jul 2020 15:17:34 +0300 [thread overview]
Message-ID: <20200724121734.GC3703480@smile.fi.intel.com> (raw)
In-Reply-To: <5c86b434fe3a47eaabf488dea14efd25@huawei.com>
On Fri, Jul 24, 2020 at 09:08:16AM +0000, Shiju Jose wrote:
> >-----Original Message-----
> >From: Bjorn Helgaas [mailto:helgaas@kernel.org]
> >Sent: 24 July 2020 00:23
> >On Wed, Jul 22, 2020 at 11:42:43AM +0100, Shiju Jose wrote:
...
> >This series is ill-formed:
I confirm this.
> > - Jul 22 5:39 Shiju Jose [PATCH v13 0/2] ACPI / APEI: Add support to not
> > - Jul 22 5:39 Shiju Jose └─>[PATCH v13 1/2] ACPI / APEI: Add a notifier
> > - Jul 22 5:42 Shiju Jose [PATCH v13 0/2] ACPI / APEI: Add support to not
> > - Jul 22 5:42 Shiju Jose └─>[PATCH v13 2/2] PCI: hip: Add handling of Hi
> git send-email failed to send out one patch each time in the patch series
> due to some internal error.
You have to fix your tools...
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-07-24 12:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 10:42 [PATCH v13 0/2] ACPI / APEI: Add support to notify the vendor specific HW errors Shiju Jose
2020-07-22 10:42 ` [PATCH v13 2/2] PCI: hip: Add handling of HiSilicon HIP PCIe controller errors Shiju Jose
2020-07-23 12:43 ` Shiju Jose
2020-07-23 23:23 ` [PATCH v13 0/2] ACPI / APEI: Add support to notify the vendor specific HW errors Bjorn Helgaas
2020-07-24 9:08 ` Shiju Jose
2020-07-24 12:17 ` andriy.shevchenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-22 10:39 Shiju Jose
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=20200724121734.GC3703480@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bp@alien8.de \
--cc=dan.carpenter@oracle.com \
--cc=helgaas@kernel.org \
--cc=james.morse@arm.com \
--cc=jonathan.cameron@huawei.com \
--cc=jroedel@suse.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=rjw@rjwysocki.net \
--cc=shiju.jose@huawei.com \
--cc=tanxiaofei@huawei.com \
--cc=tony.luck@intel.com \
--cc=wangkefeng.wang@huawei.com \
--cc=yangyicong@huawei.com \
--cc=zhangliguang@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).