linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Sanil Kumar <sanil.kumar@huawei.com>,
	Ding Tianhong <dingtianhong@huawei.com>
Cc: Alexander Graf <agraf@suse.de>,
	Mark Rutland <mark.rutland@arm.com>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Marc Zyngier <marc.zyngier@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	linuxarm@huawei.com, linux-acpi@vger.kernel.org,
	mbrugger@suse.com, linux-arm-kernel@lists.infradead.org,
	Hanjun Guo <guohanjun@huawei.com>,
	yousaf.kaukab@suse.com, Fu Wei <fu.wei@linaro.org>,
	Hanjun Guo <hanjun.guo@linaro.org>
Subject: Re: [PATCH 2/2] arch_timer: acpi: add hisi timer erratum data
Date: Thu, 16 Feb 2017 10:49:10 +0100	[thread overview]
Message-ID: <8cc0c3eb-c279-5cb1-4d6f-1a6419e0874e@linaro.org> (raw)
In-Reply-To: <58A574D9.10300@huawei.com>

On 16/02/2017 10:46, Sanil Kumar wrote:
> On 2/16/2017 3:11 PM, Ding Tianhong wrote:
>>
>> On 2017/2/16 17:32, Alexander Graf wrote:
>>>
>>> On 16/02/2017 10:14, Daniel Lezcano wrote:
>>>> On Thu, Feb 16, 2017 at 09:42:11AM +0100, Alexander Graf wrote:
>>>>
>>>> [ ... ]
>>>>
>>>>>>>> I believe Marc is looking at some rework in this area which may
>>>>>>>> enable
>>>>>>>> this, so please wait for that to appear.
>>>>>>> Yeah, I'm implementing a semi-flexible way to add new quirk
>>>>>>> types, and
>>>>>>> the last thing I want to see is two (or more) tables describing
>>>>>>> the same
>>>>>>> thing.
>>>>>> Kindly ping, if you have patches in hand, I can test against our
>>>>>> platforms,
>>>>>> thank you very much.
>>>>> Any progress on this? I'm not a big fan of stalling erratum fixes
>>>>> upstream
>>>>> because of potential future refactoring.
>>>> The fix is in the tip tree, soon in v4.11-rc1 when the merge will be
>>>> finished.
>>>>
>>>> http://goo.gl/x90qwE
>>>> http://goo.gl/asCBBD
>>> Oh, I missed that. Sorry for the fuss :).
>>>
>>>
>>> Alex
>>>
>> Hi, I thinks the tip tree is only applied the erratum for DT, not for
>> ACPI, the patch
>> for ACPI is not applied yet, so the work isn't finished. :)
> Yes, initial thread was about ACPI part. I think Alex was asking about
> that.

Ah yes. Indeed.

Thanks.


-- 
 <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog


  reply	other threads:[~2017-02-16  9:49 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-24 10:39 [PATCH 0/2] arch_timer: acpi: Add workaround for hisilicon-161010101 erratum Hanjun Guo
2017-01-24 10:39 ` [PATCH 1/2] arm64: arch_timer: acpi: Introduce a generic aquirk framework for erratum Hanjun Guo
2017-01-24 10:39 ` [PATCH 2/2] arch_timer: acpi: add hisi timer erratum data Hanjun Guo
2017-01-24 10:57   ` Mark Rutland
2017-01-24 11:32     ` Marc Zyngier
2017-01-24 12:35       ` John Garry
2017-01-24 13:08         ` Marc Zyngier
2017-01-24 13:28           ` Shameerali Kolothum Thodi
2017-01-24 13:22       ` Hanjun Guo
2017-02-10  7:10       ` Hanjun Guo
2017-02-16  8:42         ` Alexander Graf
2017-02-16  9:14           ` Daniel Lezcano
2017-02-16  9:32             ` Alexander Graf
2017-02-16  9:41               ` Ding Tianhong
2017-02-16  9:46                 ` Sanil Kumar
2017-02-16  9:49                   ` Daniel Lezcano [this message]
2017-02-16  9:42             ` Hanjun Guo
2017-02-16 10:04         ` Marc Zyngier
2017-02-20 19:00         ` Marc Zyngier
2017-02-21 11:56           ` Hanjun Guo
2017-02-21 15:22             ` Marc Zyngier
2017-02-22  4:08               ` Alexander Graf
2017-02-22  9:29                 ` Marc Zyngier
2017-02-22  7:41               ` Hanjun Guo
2017-02-21 12:46           ` Ding Tianhong
2017-01-24 13:50     ` Hanjun Guo
2017-01-24 10:49 ` [PATCH 0/2] arch_timer: acpi: Add workaround for hisilicon-161010101 erratum Hanjun Guo

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=8cc0c3eb-c279-5cb1-4d6f-1a6419e0874e@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=agraf@suse.de \
    --cc=dingtianhong@huawei.com \
    --cc=fu.wei@linaro.org \
    --cc=guohanjun@huawei.com \
    --cc=hanjun.guo@linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linuxarm@huawei.com \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=marc.zyngier@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=mbrugger@suse.com \
    --cc=rafael@kernel.org \
    --cc=sanil.kumar@huawei.com \
    --cc=will.deacon@arm.com \
    --cc=yousaf.kaukab@suse.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).