devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Lukasz Majewski <lukma@denx.de>
Cc: Shawn Guo <shawnguo@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: misc: bk4: Add device tree binding for Liebherr's BK4 SPI bus
Date: Mon, 15 Oct 2018 13:46:27 -0500	[thread overview]
Message-ID: <20181015184627.GA23207@bogus> (raw)
In-Reply-To: <20180927222655.24482-1-lukma@denx.de>

On Fri, Sep 28, 2018 at 12:26:55AM +0200, Lukasz Majewski wrote:
> Add Device Tree binding document for Liebherr's BK4 external SPI bus.
> 
> Signed-off-by: Lukasz Majewski <lukma@denx.de>
> ---
>  Documentation/devicetree/bindings/misc/lwn-bk4.txt | 26 ++++++++++++++++++++++
>  1 file changed, 26 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/misc/lwn-bk4.txt

Applied.

To add to Mark's comments, the status of binding patches can be checked 
on patchwork[1]. There's no reason for pings to me. If it is in the 
"New" state, I will get to it and you can see where you are in the 
queue. ATM, I'm rather backed up.

Rob

[1] https://patchwork.ozlabs.org/project/devicetree-bindings/list/

  parent reply	other threads:[~2018-10-15 18:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-27 22:26 [PATCH] dt-bindings: misc: bk4: Add device tree binding for Liebherr's BK4 SPI bus Lukasz Majewski
2018-10-08 12:30 ` Lukasz Majewski
2018-10-08 14:43 ` Shawn Guo
2018-10-09 10:21   ` Lukasz Majewski
2018-10-15 10:17     ` Lukasz Majewski
2018-10-15 10:24       ` Mark Brown
2018-10-15 18:46 ` Rob Herring [this message]
2018-10-15 21:23   ` Lukasz Majewski

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=20181015184627.GA23207@bogus \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukma@denx.de \
    --cc=mark.rutland@arm.com \
    --cc=shawnguo@kernel.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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).