From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: lvying6 <lvying6@huawei.com>
Cc: <linux-edac@vger.kernel.org>, <guanyalong@huawei.com>,
<wuyun.wu@huawei.com>, <tanxiaofei@huawei.com>
Subject: Re: [PATCH 0/2] rasdaemon: add support for memory Corrected Error predictive failure analysis
Date: Tue, 21 Jul 2020 14:26:32 +0200 [thread overview]
Message-ID: <20200721142632.6683caaf@coco.lan> (raw)
In-Reply-To: <1590740663-6664-1-git-send-email-lvying6@huawei.com>
Em Fri, 29 May 2020 16:24:21 +0800
lvying6 <lvying6@huawei.com> escreveu:
> rasdaemon: add support for memory Corrected Error predictive failure analysis
>
> wuyun (2):
> rasdaemon: add rbtree support for page record
> rasdaemon: add support for memory Corrected Error predictive failure
> analysis
Patches merged, thanks.
Thanks,
Mauro
next prev parent reply other threads:[~2020-07-21 12:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 8:24 [PATCH 0/2] rasdaemon: add support for memory Corrected Error predictive failure analysis lvying6
2020-05-29 8:24 ` [PATCH 1/2] rasdaemon: add rbtree support for page record lvying6
2020-05-29 12:24 ` Mauro Carvalho Chehab
2020-06-20 11:57 ` lvying
2020-05-29 8:24 ` [PATCH 2/2] rasdaemon: add support for memory Corrected Error predictive failure analysis lvying6
2020-05-29 14:31 ` Mauro Carvalho Chehab
2020-06-20 11:59 ` lvying
2020-06-20 12:26 ` [PATCH v2 rasdaemon 0/2] support memory CE " lvying6
2020-06-20 12:26 ` [PATCH v2 rasdaemon 1/2] rasdaemon: add rbtree support for page record lvying6
2020-06-20 12:26 ` [PATCH v2 rasdaemon 2/2] rasdaemon: add support for memory Corrected Error predictive failure analysis lvying6
2020-07-21 12:26 ` Mauro Carvalho Chehab [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-24 4:07 [PATCH 0/2] " lvying
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=20200721142632.6683caaf@coco.lan \
--to=mchehab@kernel.org \
--cc=guanyalong@huawei.com \
--cc=linux-edac@vger.kernel.org \
--cc=lvying6@huawei.com \
--cc=tanxiaofei@huawei.com \
--cc=wuyun.wu@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.