public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Rob Herring <robh@kernel•org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: Fixes tag needs some work in the devicetree tree
Date: Tue, 25 Jul 2023 08:32:12 +1000	[thread overview]
Message-ID: <20230725083212.0f59e6ac@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 540 bytes --]

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 :-(

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

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

next             reply	other threads:[~2023-07-24 22:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-24 22:32 Stephen Rothwell [this message]
2023-07-27  1:36 ` linux-next: Fixes tag needs some work in the devicetree tree Rob Herring
  -- 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=20230725083212.0f59e6ac@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=robh@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox