From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sivaprakash Murugesan <sivaprak@codeaurora.org>
Subject: linux-next: Fixes tag needs some work in the pinctrl tree
Date: Fri, 12 Jun 2020 07:23:19 +1000 [thread overview]
Message-ID: <20200612072319.3529b091@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 425 bytes --]
Hi all,
In commit
02e1254d7740 ("pinctrl: qcom: ipq6018 Add missing pins in qpic pin group")
Fixes tag
Fixes: ef1ea54 (pinctrl: qcom: Add ipq6018 pinctrl driver)
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 --]
next reply other threads:[~2020-06-11 21:23 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 21:23 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-07 21:20 linux-next: Fixes tag needs some work in the pinctrl tree Stephen Rothwell
2024-03-07 22:08 ` Linus Walleij
2023-08-23 22:35 Stephen Rothwell
2023-08-24 13:07 ` Asmaa Mnebhi
2023-08-25 13:45 ` Linus Walleij
2022-08-22 21:53 Stephen Rothwell
2022-08-25 12:02 ` Linus Walleij
2021-04-11 23:00 Stephen Rothwell
2021-04-12 6:40 ` Tudor.Ambarus
2020-12-06 20:16 Stephen Rothwell
2020-12-06 23:39 ` Andrew Jeffery
2020-12-08 8:26 ` Linus Walleij
2020-09-30 13:01 Stephen Rothwell
2020-09-30 13:18 ` Stephen Rothwell
2020-06-16 11:12 Stephen Rothwell
2020-06-19 4:33 ` Sivaprakash Murugesan
2020-01-09 0:28 Stephen Rothwell
2020-01-09 1:58 ` Linus Walleij
2020-01-09 2:24 ` Stephen Rothwell
2019-06-26 13:50 Stephen Rothwell
2019-06-26 14:10 ` Linus Walleij
2019-06-27 0:32 ` Nicolas Boichat
2019-06-27 1:48 ` Stephen Rothwell
2019-06-27 1:57 ` Nicolas Boichat
2019-06-27 2:01 ` Stephen Rothwell
2019-06-20 11:08 Stephen Rothwell
2019-06-25 12:15 ` Linus Walleij
2019-02-17 22:25 Stephen Rothwell
2019-02-17 22:27 ` Martin Blumenstingl
2019-02-17 22:28 ` Stephen Rothwell
2019-02-14 11:03 Stephen Rothwell
2019-02-14 11:55 ` Martin Blumenstingl
2019-02-17 21:25 ` Linus Walleij
2019-01-21 22:42 Stephen Rothwell
2019-01-22 2:20 ` Chen-Yu Tsai
2019-01-22 4:50 ` Stephen Rothwell
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=20200612072319.3529b091@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sivaprak@codeaurora.org \
/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).