linux-kernel - Re: [RESEND][PATCH 0/2] Add pl031 RTC support for Hi6220/HiKey

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 29 Jun 2016 17:30:48 -0700
From:	John Stultz <john.stultz@...aro.org>
To:	Stephen Boyd <sboyd@...eaurora.org>
Cc:	Rob Herring <robh+dt@...nel.org>,
	lkml <linux-kernel@...r.kernel.org>,
	Michael Turquette <mturquette@...libre.com>,
	Pawel Moll <pawel.moll@....com>, Wei Xu <xuwei5@...ilicon.com>,
	Guodong Xu <guodong.xu@...aro.org>,
	Zhangfei Gao <zhangfei.gao@...aro.org>
Subject: Re: [RESEND][PATCH 0/2] Add pl031 RTC support for Hi6220/HiKey

On Tue, Jun 28, 2016 at 10:15 AM, Stephen Boyd <sboyd@...eaurora.org> wrote:
> On 06/23, Rob Herring wrote:
>> On Thu, Jun 23, 2016 at 3:39 PM, John Stultz <john.stultz@...aro.org> wrote:
>> > This patchset enables the pl031 RTC on the Hi6220 SoC.
>> >
>> > I'd like to submit it for review and consideration to be merged.
>> > (But I've not gotten much feedback on it. Do I have the right
>> > people cc'ed?)
>>
>> Yes. One issue is the DT header causes dependency problems as either
>> clk or arm-soc maintainers have to take everything. I think it is
>> desired that you don't use defines in the dts file, so arm-soc can
>> take it and Michael/Stephen can take the clock changes.
>>
>> Send the dts file change to arm@...nel.org if you can't get any
>> response from the sub-arch maintainer.
>
> We can also provide a stable branch from clk tree based on
> v4.7-rc1 that you base the next patch on while sending through
> arm-soc. That sort of design has been working for a few cycles
> now.

This is fine by me. So do you mind queuing the first patch up?

Also, Since Wei acked the second patch (modulo a whitespace fix which
I'll be resending here shortly), would you want to simply to take
both, or should Wei still pull your branch in and include it into this
tree with the second patch?

I'll resend the set here in a bit, but please let me know which you'd
prefer so we don't end up with confusion around all the options of
who's doing what. :)

thanks
-john