[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <e0bab7de-1308-409c-febc-608a812592e3@gmail.com>
Date: Thu, 23 Jan 2020 15:37:22 -0800
From: Shiping Ji <shiping.linux@...il.com>
To: Rob Herring <robh+dt@...nel.org>
Cc: Borislav Petkov <bp@...en8.de>, James Morse <james.morse@....com>,
Mark Rutland <mark.rutland@....com>,
devicetree@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
linux-edac <linux-edac@...r.kernel.org>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Sasha Levin <sashal@...nel.org>, hangl@...rosoft.com,
Lei Wang <lewan@...rosoft.com>, ruizhao@...rosoft.com,
shji@...rosoft.com, Scott Branden <scott.branden@...adcom.com>,
Yuqing Shen <yuqing.shen@...adcom.com>
Subject: Re: [PATCH v10 1/2] dt-bindings: edac: dmc-520.yaml
On 1/23/2020 5:44 AM, Rob Herring wrote:
> Run 'make dt_binding_check' as that would have caught this issue on the example.
Eventually I have the dtc with yaml output built and resolved issues reported by "make dt_binding_check". Shall I submit a new v11 patch for the dt-bindings only or I should add driver code patch into v11 too?
Thanks!
--
Best regards,
Shiping Ji
Powered by blists - more mailing lists