All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xiaofei Tan <tanxiaofei@huawei.com>
To: <mchehab@kernel.org>, <linux-edac@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: <linuxarm@huawei.com>, <shiju.jose@huawei.com>,
	<jonathan.cameron@huawei.com>
Subject: Re: [PATCH rasdaemon 0/2] support l3tag&l3data decoding and one fix
Date: Tue, 19 May 2020 17:01:31 +0800	[thread overview]
Message-ID: <5EC3A06B.2020106@huawei.com> (raw)
In-Reply-To: <1584954845-21094-1-git-send-email-tanxiaofei@huawei.com>

Hi Mauro
Could you please help to review this patch set. thanks.

On 2020/3/23 17:14, Xiaofei Tan wrote:
> This patch set does two things:
> 1.add decoding for two modules, l3tag and l3data.
> 2.fix the issue that non standard decoder can't work in pthread way.
> 
> t00396350 (2):
>   rasdaemon: add support of l3tag and l3data in hip08 OEM format2
>   rasdaemon: fix the issue that non standard decoder can't work in
>     pthread way
> 
>  non-standard-hisi_hip08.c | 44 ++++++++++++++++++++++++++++++++++++++++++++
>  ras-events.c              |  8 ++------
>  2 files changed, 46 insertions(+), 6 deletions(-)
> 

-- 
 thanks
tanxiaofei


      parent reply	other threads:[~2020-05-19  9:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-23  9:14 [PATCH rasdaemon 0/2] support l3tag&l3data decoding and one fix Xiaofei Tan
2020-03-23  9:14 ` [PATCH rasdaemon 1/2] rasdaemon: add support of l3tag and l3data in hip08 OEM format2 Xiaofei Tan
2020-03-23  9:14 ` [PATCH rasdaemon 2/2] rasdaemon: fix the issue that non standard decoder can't work in pthread way Xiaofei Tan
2020-05-19  9:01 ` Xiaofei Tan [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=5EC3A06B.2020106@huawei.com \
    --to=tanxiaofei@huawei.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=mchehab+huawei@kernel.org \
    --cc=mchehab@kernel.org \
    --cc=shiju.jose@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.