From: Borislav Petkov <bp@alien8.de>
To: Shiping Ji <shiping.linux@gmail.com>
Cc: James Morse <james.morse@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-edac <linux-edac@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Sasha Levin <sashal@kernel.org>,
hangl@microsoft.com, ruizhao@microsoft.com,
Lei Wang <lewan@microsoft.com>,
Scott Branden <scott.branden@broadcom.com>,
Yuqing Shen <yuqing.shen@broadcom.com>
Subject: Re: [PATCH v11 1/2] dt-bindings: edac: dmc-520.yaml
Date: Mon, 17 Feb 2020 19:10:55 +0100 [thread overview]
Message-ID: <20200217181055.GC14426@zn.tnic> (raw)
In-Reply-To: <5354a9c3-5b5a-486a-9d19-fa9be169faef@gmail.com>
On Mon, Jan 27, 2020 at 08:23:08AM -0800, Shiping Ji wrote:
> This is the device tree bindings for new EDAC driver dmc520_edac.c.
>
> From: Lei Wang <leiwang_git@outlook.com>
>
> Signed-off-by: Lei Wang <leiwang_git@outlook.com>
> Signed-off-by: Shiping Ji <shiping.linux@gmail.com>
> Reviewed-by: James Morse <james.morse@arm.com>
>
> ---
> Changes in v11:
> - Fix issues reported by make dt_binding_check
>
> ---
> .../devicetree/bindings/edac/dmc-520.yaml | 59 +++++++++++++++++++
> 1 file changed, 59 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/edac/dmc-520.yaml
I have only this v11 patch 1/2 in my inbox and not the actual driver,
i.e., patch 2/2.
For the driver, I have v10 here:
https://lkml.kernel.org/r/83b48c70-dc06-d0d4-cae9-a2187fca628b@gmail.com
Did you send a v11 of the driver itself or should I have a look at v10?
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-02-17 18:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 16:23 [PATCH v11 1/2] dt-bindings: edac: dmc-520.yaml Shiping Ji
2020-02-05 17:48 ` Rob Herring
2020-02-17 18:10 ` Borislav Petkov [this message]
2020-02-18 17:12 ` Shiping Ji
2020-02-19 20:03 ` Borislav Petkov
2020-02-19 23:27 ` Shiping Ji
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=20200217181055.GC14426@zn.tnic \
--to=bp@alien8.de \
--cc=devicetree@vger.kernel.org \
--cc=hangl@microsoft.com \
--cc=james.morse@arm.com \
--cc=lewan@microsoft.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=ruizhao@microsoft.com \
--cc=sashal@kernel.org \
--cc=scott.branden@broadcom.com \
--cc=shiping.linux@gmail.com \
--cc=yuqing.shen@broadcom.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 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.