From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the pinctrl tree
Date: Sun, 17 Feb 2019 23:27:35 +0100 [thread overview]
Message-ID: <CAFBinCCOqBumiAm6hM0MhVwPrUZydvvvOhrS34wTWRo6Jy87yA@mail.gmail.com> (raw)
In-Reply-To: <20190218092536.39375e84@canb.auug.org.au>
Hi Stephen,
On Sun, Feb 17, 2019 at 11:25 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi Linus,
>
> In commit
>
> a5a0bbca16cd ("pinctrl: meson: meson8b: fix the sdxc_a data 1..3 pins")
>
> Fixes tag
>
> Fixes: 0fefcb6 ("pinctrl: Add support for Meson8b")
>
> 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").
Linus fixed this one hour ago in the linux-pinctrl tree
so this should be gone with your next run
Regards
Martin
next prev parent reply other threads:[~2019-02-17 22:27 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-17 22:25 linux-next: Fixes tag needs some work in the pinctrl tree Stephen Rothwell
2019-02-17 22:27 ` Martin Blumenstingl [this message]
2019-02-17 22:28 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2024-03-07 21:20 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-06-11 21:23 Stephen Rothwell
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-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=CAFBinCCOqBumiAm6hM0MhVwPrUZydvvvOhrS34wTWRo6Jy87yA@mail.gmail.com \
--to=martin.blumenstingl@googlemail.com \
--cc=linus.walleij@linaro.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 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).