public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Rob Herring <robherring2@gmail.com>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the devicetree tree
Date: Tue, 24 Dec 2019 11:44:10 +0100	[thread overview]
Message-ID: <20191224114410.0d72c72f@xps13> (raw)
In-Reply-To: <20191221143211.47eea79d@canb.auug.org.au>

Hi Stephen, Rob,

Stephen Rothwell <sfr@canb.auug.org.au> wrote on Sat, 21 Dec 2019
14:32:11 +1100:

> Hi all,
> 
> n commit
> 
>   13670c493ab8 ("dt-bindings: phy: Fix the PX30 DSI PHY compatible in the example")
> 
> Fixes tag
> 
>   Fixes: 3200df7fa1d6 ("dt-bindings: phy: add yaml binding for rockchip,px30-dsi-dphy")
> 
> has these problem(s):
> 
>   - Target SHA1 does not exist
> 
> Maybe you meant
> 
> Fixes: 3817c7961179 ("dt-bindings: phy: add yaml binding for rockchip,px30-dsi-dphy")

Sorry for the mistake, I took the hash from Heiko's tree. This is
indeed the right one.

Thanks,
Miquèl

  reply	other threads:[~2019-12-24 10:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-21  3:32 linux-next: Fixes tag needs some work in the devicetree tree Stephen Rothwell
2019-12-24 10:44 ` Miquel Raynal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-11  2:18 Stephen Rothwell
2023-07-24 22:32 Stephen Rothwell
2023-07-27  1:36 ` Rob Herring
2022-01-08  7:25 Stephen Rothwell
2022-01-08 14:51 ` Rob Herring
2021-06-20 22:42 Stephen Rothwell
2021-06-21 14:38 ` Sean Anderson
2021-06-21 21:06   ` Stephen Rothwell
2021-06-21 23:20     ` Rob Herring
2019-11-23 10:37 Stephen Rothwell
2019-04-10 21:27 Stephen Rothwell
2019-04-10 21:34 ` 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=20191224114410.0d72c72f@xps13 \
    --to=miquel.raynal@bootlin.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=robherring2@gmail.com \
    --cc=sfr@canb.auug.org.au \
    /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