From: Ding Tianhong <dingtianhong-hv44wF8Li93QT0dZR+AlfA@public.gmane.org> To: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org> Cc: Catalin Marinas <catalin.marinas-5wv7dgnIgG8@public.gmane.org>, Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>, Marc Zyngier <marc.zyngier-5wv7dgnIgG8@public.gmane.org>, Scott Wood <oss-fOR+EgIDQEHk1uMJSBkQmQ@public.gmane.org>, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Shawn Guo <shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>, stuart.yoder-3arQi8VN3Tc@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org Subject: Re: [PATCH 1/3] arm64: arch_timer: Add device tree binding for hisilicon-161x01 erratum Date: Mon, 24 Oct 2016 21:23:10 +0800 [thread overview] Message-ID: <1dcfb21a-7417-282e-f187-425d2c148672@huawei.com> (raw) In-Reply-To: <20161024131617.GJ15620@leverpostej> On 2016/10/24 21:16, Mark Rutland wrote: > On Mon, Oct 24, 2016 at 08:40:01PM +0800, Ding Tianhong wrote: >> On 2016/10/24 19:16, Mark Rutland wrote: >>> Is "161x01" the *exact* erratum number, or is the 'x' a wildcard? >> >> The 'x' is a wildcard, it will cover 161001 to 161601 several numbers, > > Given you're using a wildcard, I take it that this is a *part* number? > Yes, I was doubt how to fix this, should I choose a better erratum number? > Thanks, > Mark. > > . > -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: dingtianhong@huawei.com (Ding Tianhong) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 1/3] arm64: arch_timer: Add device tree binding for hisilicon-161x01 erratum Date: Mon, 24 Oct 2016 21:23:10 +0800 [thread overview] Message-ID: <1dcfb21a-7417-282e-f187-425d2c148672@huawei.com> (raw) In-Reply-To: <20161024131617.GJ15620@leverpostej> On 2016/10/24 21:16, Mark Rutland wrote: > On Mon, Oct 24, 2016 at 08:40:01PM +0800, Ding Tianhong wrote: >> On 2016/10/24 19:16, Mark Rutland wrote: >>> Is "161x01" the *exact* erratum number, or is the 'x' a wildcard? >> >> The 'x' is a wildcard, it will cover 161001 to 161601 several numbers, > > Given you're using a wildcard, I take it that this is a *part* number? > Yes, I was doubt how to fix this, should I choose a better erratum number? > Thanks, > Mark. > > . >
next prev parent reply other threads:[~2016-10-24 13:23 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-10-23 3:21 [PATCH 1/3] arm64: arch_timer: Add device tree binding for hisilicon-161x01 erratum Ding Tianhong 2016-10-23 3:21 ` Ding Tianhong [not found] ` <962ea92f-870b-e1d0-5bb7-1a6d66c35122-hv44wF8Li93QT0dZR+AlfA@public.gmane.org> 2016-10-23 12:04 ` Shawn Guo 2016-10-23 12:04 ` Shawn Guo 2016-10-24 5:46 ` Ding Tianhong 2016-10-24 5:46 ` Ding Tianhong 2016-10-24 8:36 ` Marc Zyngier 2016-10-24 8:36 ` Marc Zyngier [not found] ` <3a29c03a-2da1-7bfe-28ff-21dada50ee8d-5wv7dgnIgG8@public.gmane.org> 2016-10-24 8:43 ` Ding Tianhong 2016-10-24 8:43 ` Ding Tianhong 2016-10-24 11:16 ` Mark Rutland 2016-10-24 11:16 ` Mark Rutland 2016-10-24 12:40 ` Ding Tianhong 2016-10-24 12:40 ` Ding Tianhong [not found] ` <7e839df8-f8f7-3b16-8321-4ff45b6c5884-hv44wF8Li93QT0dZR+AlfA@public.gmane.org> 2016-10-24 13:16 ` Mark Rutland 2016-10-24 13:16 ` Mark Rutland 2016-10-24 13:23 ` Ding Tianhong [this message] 2016-10-24 13:23 ` Ding Tianhong [not found] ` <1dcfb21a-7417-282e-f187-425d2c148672-hv44wF8Li93QT0dZR+AlfA@public.gmane.org> 2016-10-24 13:39 ` Mark Rutland 2016-10-24 13:39 ` Mark Rutland 2016-10-26 2:59 ` Ding Tianhong 2016-10-26 2:59 ` Ding Tianhong
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=1dcfb21a-7417-282e-f187-425d2c148672@huawei.com \ --to=dingtianhong-hv44wf8li93qt0dzr+alfa@public.gmane.org \ --cc=catalin.marinas-5wv7dgnIgG8@public.gmane.org \ --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \ --cc=marc.zyngier-5wv7dgnIgG8@public.gmane.org \ --cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \ --cc=oss-fOR+EgIDQEHk1uMJSBkQmQ@public.gmane.org \ --cc=shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \ --cc=stuart.yoder-3arQi8VN3Tc@public.gmane.org \ --cc=will.deacon-5wv7dgnIgG8@public.gmane.org \ /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: linkBe 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.