From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dmitry Osipenko <digetx@gmail.com>
Subject: Re: linux-next: Fixes tag needs some work in the clockevents tree
Date: Thu, 13 Jun 2019 08:52:21 +0200 [thread overview]
Message-ID: <1b6c715b-5aa9-b0c1-d228-c99d2adc57b4@linaro.org> (raw)
In-Reply-To: <20190613090700.04badfc3@canb.auug.org.au>
On 13/06/2019 01:07, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 98793726ab3f ("clocksource/drivers/tegra: Restore timer rate on Tegra210")
>
> Fixes tag
>
> Fixes: 3be2a85a0b61 ("Support per-CPU timers on all Tegra's")
>
> has these problem(s):
>
> - Subject does not match target commit subject
> Just use
> git log -1 --format='Fixes: %h ("%s")'
Hi Stephen,
actually it returns:
git log -1 --format='Fixes: %h ("%s")' 3be2a85a0b61
Fixes: 3be2a85a0b61 ("clocksource/drivers/tegra: Support per-CPU timers
on all Tegra's")
Is it ok to shorten the subject?
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2019-06-13 16:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 23:07 linux-next: Fixes tag needs some work in the clockevents tree Stephen Rothwell
2019-06-13 6:52 ` Daniel Lezcano [this message]
2019-06-16 13:24 ` Stephen Rothwell
2019-06-16 14:08 ` Dmitry Osipenko
2019-06-16 14:18 ` Daniel Lezcano
2019-06-16 14:30 ` Dmitry Osipenko
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=1b6c715b-5aa9-b0c1-d228-c99d2adc57b4@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=digetx@gmail.com \
--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).