All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: 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: Wed, 26 Jul 2023 19:36:55 -0600	[thread overview]
Message-ID: <CAL_JsqKpDO4gtSBn=P1OdArY_s8Za0z7LTiAF3-=Ri5Bt+UfEQ@mail.gmail.com> (raw)
In-Reply-To: <20230725083212.0f59e6ac@canb.auug.org.au>

On Mon, Jul 24, 2023 at 4:32 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> In commit
>
>   120e4bb6ca34 ("of: fix htmldocs build warnings")
>
> Fixes tag
>
>   Fixes: 39459ce717b8 ("of: dynamic: add lifecycle docbook info to node creation functions")
>
> has these problem(s):
>
>   - Target SHA1 does not exist
>
> Maybe you meant
>
> Fixes: d9194e009efe ("of: dynamic: add lifecycle docbook info to node creation functions")
>
> I assume somthing has been rebased along the way :-(

Probably, but the above commit was committed Feb 20. You first sent a
patch on Mar 22.

> Also, please keep all the commit message tags together at the end of
> the commit message.

Looks like b4 was confused by "Reported by" (space instead of hyphen).

Anyways, both now fixed.

Thanks,
Rob

  reply	other threads:[~2023-07-27  1:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-24 22:32 linux-next: Fixes tag needs some work in the devicetree tree Stephen Rothwell
2023-07-27  1:36 ` Rob Herring [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-11  2:18 Stephen Rothwell
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-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_JsqKpDO4gtSBn=P1OdArY_s8Za0z7LTiAF3-=Ri5Bt+UfEQ@mail.gmail.com' \
    --to=robh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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 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.