From: Rob Herring <robherring2@gmail.com>
To: Stephen Rothwell <sfr@rothwell.id.au>,
Sean Anderson <sean.anderson@seco.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
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: Mon, 21 Jun 2021 17:20:58 -0600 [thread overview]
Message-ID: <CAL_Jsq+6gM5U2yALJfaE+GUeivPnAwUOTy65=2M1s8NLZMRD9w@mail.gmail.com> (raw)
In-Reply-To: <20210622070617.19517119@elm.ozlabs.ibm.com>
On Mon, Jun 21, 2021 at 3:06 PM Stephen Rothwell <sfr@rothwell.id.au> wrote:
>
> 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.
I've fixed it up.
Rob
next prev parent reply other threads:[~2021-06-21 23:21 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
2021-06-21 23:20 ` Rob Herring [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
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='CAL_Jsq+6gM5U2yALJfaE+GUeivPnAwUOTy65=2M1s8NLZMRD9w@mail.gmail.com' \
--to=robherring2@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=luca@lucaceresoli.net \
--cc=sean.anderson@seco.com \
--cc=sfr@canb.auug.org.au \
--cc=sfr@rothwell.id.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 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.