From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Robert Marko <robimarko@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Andy Gross <agross@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the qcom tree
Date: Sun, 13 Feb 2022 20:53:04 -0800 [thread overview]
Message-ID: <YgngMN+lKaW3fYp5@ripper> (raw)
In-Reply-To: <CAOX2RU5NzOK+d-QEMsOiSPX85M2_B44SeJUteZepsyZny7fgnQ@mail.gmail.com>
On Sun 13 Feb 03:52 PST 2022, Robert Marko wrote:
> On Sun, 13 Feb 2022 at 11:39, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Hi all,
> >
> > In commit
> >
> > bf8f5182b8f5 ("clk: qcom: ipq8074: fix PCI-E clock oops")
> >
> > Fixes tag
> >
> > Fixes: f0cfcf1a ("clk: qcom: ipq8074: Add missing clocks for pcie")
> >
> > has these problem(s):
> >
> > - SHA1 should be at least 12 digits long
> > Can be fixed for the future 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").
>
> Hi Stephen,
>
> Sorry for the short hash, don't know how this happened.
> Do you want me to send a v3 with the fixed hash?
>
No need, I could update the commit as is. But given that I would have to
rebase 20 other patches I'm hesitant to fix it.
Given that checkpatch catches this issue in commit references in the
message and other issues in Fixes I was expecting it to catch this one
as well... Will make sure to look for this going forward (or perhaps
figure out how to improve checkpatch...)
Thanks,
Bjorn
next prev parent reply other threads:[~2022-02-14 4:50 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-13 10:39 linux-next: Fixes tag needs some work in the qcom tree Stephen Rothwell
2022-02-13 11:52 ` Robert Marko
2022-02-13 21:02 ` Stephen Rothwell
2022-02-14 4:53 ` Bjorn Andersson [this message]
2022-02-16 9:59 ` Robert Marko
-- strict thread matches above, loose matches on Subject: below --
2024-02-07 7:05 Stephen Rothwell
2023-07-23 22:53 Stephen Rothwell
2023-05-29 21:49 Stephen Rothwell
2023-05-30 14:56 ` Bjorn Andersson
2023-05-31 13:25 ` Linus Walleij
2023-03-14 21:15 Stephen Rothwell
2023-03-13 21:37 Stephen Rothwell
2023-02-09 4:04 Stephen Rothwell
2023-02-09 10:02 ` Bartosz Golaszewski
2023-02-05 21:09 Stephen Rothwell
2023-01-19 6:04 Stephen Rothwell
2022-10-03 20:13 Stephen Rothwell
2022-09-14 7:23 Stephen Rothwell
2022-04-13 21:40 Stephen Rothwell
2022-04-14 15:03 ` Konrad Dybcio
2022-03-09 12:10 Stephen Rothwell
2021-11-22 21:08 Stephen Rothwell
2021-09-20 22:24 Stephen Rothwell
2021-09-21 23:02 ` Stephen Rothwell
2021-09-21 23:31 ` Bjorn Andersson
2021-09-22 0:15 ` Stephen Rothwell
2021-07-20 7:25 Stephen Rothwell
2021-01-21 7:41 Stephen Rothwell
2021-01-21 8:50 ` Robert Foss
2020-02-12 7:18 Stephen Rothwell
2019-02-07 13:47 Stephen Rothwell
2019-02-07 17:06 ` Doug Anderson
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=YgngMN+lKaW3fYp5@ripper \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=robimarko@gmail.com \
--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).