From mboxrd@z Thu Jan 1 00:00:00 1970 From: dingtianhong@huawei.com (Ding Tianhong) Date: Thu, 8 Sep 2016 20:31:36 +0800 Subject: [PATCH v4 1/4] arm64: arch_timer: Add device tree binding for A-008585 erratum In-Reply-To: <57D15497.9030606@arm.com> References: <1467877572-10817-1-git-send-email-oss@buserror.net> <57D14F9A.2050007@huawei.com> <57D15497.9030606@arm.com> Message-ID: <57D15A28.8040807@huawei.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 2016/9/8 20:07, Marc Zyngier wrote: > On 08/09/16 12:46, Ding Tianhong wrote: >> Ping > > Oh please! Maybe you could look at the couple of points I've raised in > this thread and help addressing them, given that you have a vested > interest in seeing these patches being merged? Pinging people this way > is not very productive. > > Thanks, > Ok, I miss that patch, I will review your command and feedback, thanks. Ding > M. > >> >> On 2016/8/25 19:04, Matthias Brugger wrote: >>> Hi all, >>> >>> On 07/07/16 09:46, Scott Wood wrote: >>>> This erratum describes a bug in logic outside the core, so MIDR can't be >>>> used to identify its presence, and reading an SoC-specific revision >>>> register from common arch timer code would be awkward. So, describe it >>>> in the device tree. >>>> >>>> Signed-off-by: Scott Wood >>>> Acked-by: Rob Herring >>>> --- >>> >>> As of today I wasn't able to find this series in linux-next. Was this series somehow forgotten? Scott maybe you can resend the patches adding the clocksource maintainer. >>> >>> Regards, >>> Matthias >>> >>> _______________________________________________ >>> linux-arm-kernel mailing list >>> linux-arm-kernel at lists.infradead.org >>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel >>> >>> >> >> > > From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ding Tianhong Subject: Re: [PATCH v4 1/4] arm64: arch_timer: Add device tree binding for A-008585 erratum Date: Thu, 8 Sep 2016 20:31:36 +0800 Message-ID: <57D15A28.8040807@huawei.com> References: <1467877572-10817-1-git-send-email-oss@buserror.net> <57D14F9A.2050007@huawei.com> <57D15497.9030606@arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <57D15497.9030606@arm.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Marc Zyngier , Matthias Brugger , Scott Wood , Catalin Marinas , Will Deacon Cc: devicetree@vger.kernel.org, stuart.yoder@nxp.com, linux-arm-kernel@lists.infradead.org, Russell King List-Id: devicetree@vger.kernel.org On 2016/9/8 20:07, Marc Zyngier wrote: > On 08/09/16 12:46, Ding Tianhong wrote: >> Ping > > Oh please! Maybe you could look at the couple of points I've raised in > this thread and help addressing them, given that you have a vested > interest in seeing these patches being merged? Pinging people this way > is not very productive. > > Thanks, > Ok, I miss that patch, I will review your command and feedback, thanks. Ding > M. > >> >> On 2016/8/25 19:04, Matthias Brugger wrote: >>> Hi all, >>> >>> On 07/07/16 09:46, Scott Wood wrote: >>>> This erratum describes a bug in logic outside the core, so MIDR can't be >>>> used to identify its presence, and reading an SoC-specific revision >>>> register from common arch timer code would be awkward. So, describe it >>>> in the device tree. >>>> >>>> Signed-off-by: Scott Wood >>>> Acked-by: Rob Herring >>>> --- >>> >>> As of today I wasn't able to find this series in linux-next. Was this series somehow forgotten? Scott maybe you can resend the patches adding the clocksource maintainer. >>> >>> Regards, >>> Matthias >>> >>> _______________________________________________ >>> linux-arm-kernel mailing list >>> linux-arm-kernel@lists.infradead.org >>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel >>> >>> >> >> > >