linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Rob Herring <robherring2@gmail.com>
Cc: Baruch Siach <baruch@tkos.co.il>,
	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: Sat, 8 Jan 2022 18:25:38 +1100	[thread overview]
Message-ID: <20220108182538.362c8e29@canb.auug.org.au> (raw)

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

Hi all,

In commit

  86ce070ce00a ("of: base: Fix phandle argument length mismatch error message")

Fixes tag

  Fixes: af3be70a321 ("of: Improve of_phandle_iterator_next() error message")

has these problem(s):

  - SHA1 should be at least 12 digits long
    Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
    or later) just making sure it is not set (or set to "auto").

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2022-01-08  7:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-08  7:25 Stephen Rothwell [this message]
2022-01-08 14:51 ` 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
2023-07-24 22:32 Stephen Rothwell
2023-07-27  1:36 ` 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=20220108182538.362c8e29@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=baruch@tkos.co.il \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=robherring2@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).