From: Olof Johansson <olof@lixom.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Arnd Bergmann <arnd@arndb.de>,
ARM <linux-arm-kernel@lists.infradead.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Benjamin Gaignard <benjamin.gaignard@st.com>,
Alexandre Torgue <alexandre.torgue@st.com>
Subject: Re: linux-next: Fixes tag needs some work in the arm-soc tree
Date: Sun, 12 Jan 2020 12:01:32 -0800 [thread overview]
Message-ID: <CAOesGMjZQTjos9fU52zsrKFZj9LVE3oUXQFpjJov3-dBD0cT+w@mail.gmail.com> (raw)
In-Reply-To: <20200113065622.15eb3c87@canb.auug.org.au>
Stephen,
On Sun, Jan 12, 2020 at 11:56 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> n commit
>
> 0ff15a86d0c5 ("ARM: dts: stm32: Add power-supply for DSI panel on stm32f469-disco")
>
> Fixes tag
>
> Fixes: 18c8866266 ("ARM: dts: stm32: Add display support on stm32f469-disco")
>
> 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").
>
> Also, please keep the commit message tags together.
Thanks for the report, we'll keep an eye out for these formatting
tweaks in the future.
Alexandre; no respin needed to fix this IMHO, just something to keep in mind.
-Olof
next prev parent reply other threads:[~2020-01-12 20:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-12 19:56 linux-next: Fixes tag needs some work in the arm-soc tree Stephen Rothwell
2020-01-12 20:01 ` Olof Johansson [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-28 15:51 Stephen Rothwell
2022-02-28 15:57 ` Arnd Bergmann
2020-10-05 9:21 Stephen Rothwell
2019-11-14 9:21 Stephen Rothwell
2019-11-14 11:01 ` Sudeep Holla
2019-09-04 21:24 Stephen Rothwell
2019-08-15 21:43 Stephen Rothwell
2019-08-15 10:10 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=CAOesGMjZQTjos9fU52zsrKFZj9LVE3oUXQFpjJov3-dBD0cT+w@mail.gmail.com \
--to=olof@lixom.net \
--cc=alexandre.torgue@st.com \
--cc=arnd@arndb.de \
--cc=benjamin.gaignard@st.com \
--cc=linux-arm-kernel@lists.infradead.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).