From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Shiju Jose <shiju.jose@huawei.com>
Cc: "linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
Linuxarm <linuxarm@huawei.com>,
tanxiaofei <tanxiaofei@huawei.com>
Subject: Re: [PATCH v3 0/7] rasdaemon: Add support for memory_failure events and vendor errors
Date: Wed, 26 May 2021 09:21:56 +0200 [thread overview]
Message-ID: <20210526092156.0da6a9be@coco.lan> (raw)
In-Reply-To: <45ad6a601f2c4dd1a66babdedecb1273@huawei.com>
Em Thu, 13 May 2021 08:55:02 +0000
Shiju Jose <shiju.jose@huawei.com> escreveu:
> Hi Mauro,
>
> Ping...
> Any comments on this series?
Applied, thanks!
Next time, it would be better to use github[1], as it is easier for me to
track what's pending to review ;-)
[1] https://github.com/mchehab/rasdaemon
Regards,
Mauro
>
> Thanks,
> Shiju
>
> >-----Original Message-----
> >From: Shiju Jose
> >Sent: 08 March 2021 16:57
> >To: linux-edac@vger.kernel.org; mchehab+huawei@kernel.org
> >Cc: Linuxarm <linuxarm@huawei.com>; tanxiaofei
> ><tanxiaofei@huawei.com>; Shiju Jose <shiju.jose@huawei.com>
> >Subject: [PATCH v3 0/7] rasdaemon: Add support for memory_failure events
> >and vendor errors
> >
> >1. Add support for the memory_failure trace event in the rasdaemon.
> >2. Add improvements & support for the vendor specific errors into the
> >util/ras-mc-ctl.in script.
> >
> >Changes:
> >v2 -> v3
> >Re-based and removed fix patch for the ras-mc-ctl exception as another fix
> >patch merged recently.
> >
> >v1 -> v2
> >1. Fix the feedback by Mauro for the fix patch for the exception
> > in the ras-mc-ctl.in.
> >2. Rebased and grouped the previous v1 rasdaemon patches posted.
> >
> >Shiju Jose (7):
> > rasdaemon: add support for memory_failure events
> > rasdaemon: ras-mc-ctl: Modify ARM processor error summary log
> > rasdaemon: ras-mc-ctl: Add memory failure events
> > rasdaemon: ras-mc-ctl: Add support for the vendor-specific errors
> > rasdaemon: ras-mc-ctl: Add support for HiSilicon Kunpeng920 errors
> > rasdaemon: ras-mc-ctl: Add support for HiSilicon Kunpeng9xx common
> > errors
> > rasdaemon: Modify confiure.ac for Hisilicon Kunpeng errors
> >
> > .travis.yml | 2 +-
> > Makefile.am | 7 +-
> > configure.ac | 13 +-
> > ras-events.c | 15 ++
> > ras-events.h | 1 +
> > ras-memory-failure-handler.c | 179 +++++++++++++++++++++ ras-memory-
> >failure-handler.h | 25 +++
> > ras-record.c | 70 ++++++++
> > ras-record.h | 13 ++
> > ras-report.c | 68 ++++++++
> > ras-report.h | 2 +
> > util/ras-mc-ctl.in | 303 ++++++++++++++++++++++++++++++++++-
> > 12 files changed, 688 insertions(+), 10 deletions(-) create mode 100644 ras-
> >memory-failure-handler.c create mode 100644 ras-memory-failure-handler.h
> >
> >--
> >2.17.1
>
Thanks,
Mauro
prev parent reply other threads:[~2021-05-26 7:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 16:57 [PATCH v3 0/7] rasdaemon: Add support for memory_failure events and vendor errors Shiju Jose
2021-03-08 16:57 ` [PATCH v3 1/7] rasdaemon: add support for memory_failure events Shiju Jose
2021-03-08 16:57 ` [PATCH v3 2/7] rasdaemon: ras-mc-ctl: Modify ARM processor error summary log Shiju Jose
2021-03-08 16:57 ` [PATCH v3 3/7] rasdaemon: ras-mc-ctl: Add memory failure events Shiju Jose
2021-03-08 16:57 ` [PATCH v3 4/7] rasdaemon: ras-mc-ctl: Add support for the vendor-specific errors Shiju Jose
2021-03-08 16:57 ` [PATCH v3 5/7] rasdaemon: ras-mc-ctl: Add support for HiSilicon Kunpeng920 errors Shiju Jose
2021-03-08 16:57 ` [PATCH v3 6/7] rasdaemon: ras-mc-ctl: Add support for HiSilicon Kunpeng9xx common errors Shiju Jose
2021-03-08 16:57 ` [PATCH v3 7/7] rasdaemon: Modify confiure.ac for Hisilicon Kunpeng errors Shiju Jose
2021-05-13 8:55 ` [PATCH v3 0/7] rasdaemon: Add support for memory_failure events and vendor errors Shiju Jose
2021-05-26 7:21 ` Mauro Carvalho Chehab [this message]
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=20210526092156.0da6a9be@coco.lan \
--to=mchehab+huawei@kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=shiju.jose@huawei.com \
--cc=tanxiaofei@huawei.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 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.