devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca@lucaceresoli.net>
To: linux-clk@vger.kernel.org
Cc: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Marek Vasut <marek.vasut@gmail.com>,
	Adam Ford <aford173@gmail.com>
Subject: Re: [PATCH v2 1/4] dt-bindings: clk: versaclock5: fix 'idt' prefix typos
Date: Wed, 8 Jul 2020 18:56:15 +0200	[thread overview]
Message-ID: <84f1800d-e8a4-52d8-e7f7-a199601c2fea@lucaceresoli.net> (raw)
In-Reply-To: <20200708074035.31595-1-luca@lucaceresoli.net>

Hi,

On 08/07/20 09:40, Luca Ceresoli wrote:
> 'idt' is misspelled 'itd' in a few places, fix it.
> 
> Fixes: 34662f6e3084 ("dt: Add additional option bindings for IDT VersaClock")

This line triggers a warning in patchwork:

WARNING: Unknown commit id '34662f6e3084', maybe rebased or not pulled?

The commit is in the clk-next branch of
git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git, and thus
supposed to be merged into mainline.

-- 
Luca

  parent reply	other threads:[~2020-07-08 16:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-08  7:40 [PATCH v2 1/4] dt-bindings: clk: versaclock5: fix 'idt' prefix typos Luca Ceresoli
2020-07-08  7:40 ` [PATCH v2 2/4] MAINTAINERS: take over IDT VersaClock 5 clock driver Luca Ceresoli
2020-07-08  7:40 ` [PATCH v2 3/4] clk: vc5: use a dedicated struct to describe the output drivers Luca Ceresoli
2020-07-08  7:40 ` [PATCH v2 4/4] dt-bindings: clk: versaclock5: convert to yaml Luca Ceresoli
2020-07-14  3:11   ` Rob Herring
2020-07-14  9:15     ` Luca Ceresoli
2020-07-14 14:51       ` Rob Herring
2020-07-21 16:40     ` Luca Ceresoli
2020-07-08 16:56 ` Luca Ceresoli [this message]
2020-07-14  3:06 ` [PATCH v2 1/4] dt-bindings: clk: versaclock5: fix 'idt' prefix typos Rob Herring

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=84f1800d-e8a4-52d8-e7f7-a199601c2fea@lucaceresoli.net \
    --to=luca@lucaceresoli.net \
    --cc=aford173@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marek.vasut@gmail.com \
    --cc=mturquette@baylibre.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@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).