mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Baicar, Tyler" <tbaicar@codeaurora.org>
To: Borislav Petkov <bp@suse.de>, gengdongjiu <gengdj.1984@gmail.com>
Cc: rjw@rjwysocki.net, lenb@kernel.org, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org, linuxarm@huawei.com,
	john.garry@huawei.com, shiju.jose@huawei.com,
	zhengqiang10@huawei.com, wangxiongfeng2@huawei.com,
	huangshaoyu@huawei.com, wuquanming@huawei.com,
	james.morse@arm.com, geliangtang@gmail.com,
	andriy.shevchenko@linux.intel.com, tony.luck@intel.com,
	austinwc@codeaurora.org, shameerali.kolothum.thodi@huawei.com,
	jonathan.cameron@huawei.com, huangdaode@hisilicon.com,
	wangzhou1@hisilicon.com
Subject: Re: [PATCH v2] acpi: apei: fix the wrongly iterate generic error status block
Date: Tue, 15 Aug 2017 12:31:14 -0600	[thread overview]
Message-ID: <7921a233-6971-6e3b-9164-01d6176d61c0@codeaurora.org> (raw)
In-Reply-To: <20170815165551.4cwa344wm6eptj3d@pd.tnic>

On 8/15/2017 10:55 AM, Borislav Petkov wrote:
> On Wed, Aug 16, 2017 at 12:42:43AM +0800, gengdongjiu wrote:
>> I ever discuss it with Tyler about it, as shown below link, thanks
>>
>> https://lkml.org/lkml/2017/8/14/355
> Tyler's patch fixes ghes_do_proc() - yours cper_estatus_print(). How is
> that merged?
>
Hello Boris,

His patch fixes the define for apei_estatus_for_each_section which in 
turn should fix ghes_do_proc(). So my patch should no longer be needed. 
I'm going to test this out just to verify if fixes the issue I found.

Dongjiu,

This patch changes cper_estatus_print() to use 
apei_estatus_for_each_section. Can you also make that same change to 
cper_estatus_check() since that function is doing the same iteration?

Thanks,
Tyler

-- 
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.

  reply	other threads:[~2017-08-15 18:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-15 11:15 Dongjiu Geng
2017-08-15 14:16 ` gengdongjiu
2017-08-15 16:13   ` Borislav Petkov
2017-08-15 16:30     ` gengdongjiu
2017-08-15 16:32       ` Borislav Petkov
2017-08-15 16:42         ` gengdongjiu
2017-08-15 16:55           ` Borislav Petkov
2017-08-15 18:31             ` Baicar, Tyler [this message]
2017-08-15 19:12               ` Borislav Petkov
2017-08-15 21:34               ` gengdongjiu
2017-08-15 23:26                 ` Baicar, Tyler
2017-08-16  8:03                   ` gengdongjiu

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=7921a233-6971-6e3b-9164-01d6176d61c0@codeaurora.org \
    --to=tbaicar@codeaurora.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=austinwc@codeaurora.org \
    --cc=bp@suse.de \
    --cc=geliangtang@gmail.com \
    --cc=gengdj.1984@gmail.com \
    --cc=huangdaode@hisilicon.com \
    --cc=huangshaoyu@huawei.com \
    --cc=james.morse@arm.com \
    --cc=john.garry@huawei.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=rjw@rjwysocki.net \
    --cc=shameerali.kolothum.thodi@huawei.com \
    --cc=shiju.jose@huawei.com \
    --cc=tony.luck@intel.com \
    --cc=wangxiongfeng2@huawei.com \
    --cc=wangzhou1@hisilicon.com \
    --cc=wuquanming@huawei.com \
    --cc=zhengqiang10@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®