From: Stephen Rothwell <sfr@rothwell•id.au>
To: Sean Anderson <sean.anderson@seco•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Rob Herring <robherring2@gmail•com>,
Luca Ceresoli <luca@lucaceresoli•net>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the devicetree tree
Date: Tue, 22 Jun 2021 07:06:17 +1000 [thread overview]
Message-ID: <20210622070617.19517119@elm.ozlabs.ibm.com> (raw)
In-Reply-To: <456f4183-aa2e-b714-e681-819485f222a1@seco.com>
[-- Attachment #1: Type: text/plain, Size: 627 bytes --]
Hi Sean,
On Mon, 21 Jun 2021 10:38:32 -0400 Sean Anderson <sean.anderson@seco•com> wrote:
>
> On 6/20/21 6:42 PM, Stephen Rothwell wrote:
> >
> > In commit
> >
> > f92f2726e3dd ("dt-bindings: clk: vc5: Fix example")
> >
> > Fixes tag
> >
> > Fixes: 766e1b8608bf ("dt-bindings: clk: versaclock5: convert to yaml")
> >
> > has these problem(s):
> >
> > - Target SHA1 does not exist
> >
> > Maybe you meant
> >
> > Fixes: 45c940184b50 ("dt-bindings: clk: versaclock5: convert to yaml")
>
> Ah, yes I do. Should I submit a v2?
Thats up to Rob, really.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-06-21 21:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-20 22:42 linux-next: Fixes tag needs some work in the devicetree tree Stephen Rothwell
2021-06-21 14:38 ` Sean Anderson
2021-06-21 21:06 ` Stephen Rothwell [this message]
2021-06-21 23:20 ` Rob Herring
-- 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
2019-12-21 3:32 Stephen Rothwell
2019-12-24 10:44 ` Miquel Raynal
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=20210622070617.19517119@elm.ozlabs.ibm.com \
--to=sfr@rothwell$(echo .)id.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=luca@lucaceresoli$(echo .)net \
--cc=robherring2@gmail$(echo .)com \
--cc=sean.anderson@seco$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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