From: Sebastian Reichel <sre@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Tony Lindgren <tony@atomide.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tags need some work in the battery tree
Date: Thu, 14 Jan 2021 23:47:52 +0100 [thread overview]
Message-ID: <20210114224752.4ohn7zmrcyde474n@earth.universe> (raw)
In-Reply-To: <20210115092301.4c1f4893@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]
Hi Stephen,
On Fri, Jan 15, 2021 at 09:23:01AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> c339b3aec780 ("power: supply: cpcap-battery: Fix missing power_supply_put()")
>
> Fixes tag
>
> Fixes: b0134cc14b9 ("power: supply: cpcap-battery: Fix handling of lowered charger voltage")
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Maybe you meant
>
> Fixes: 8b0134cc14b9 ("power: supply: cpcap-battery: Fix handling of lowered charger voltage")
>
> In commit
>
> efa32492629a ("power: supply: cpcap-charger: Fix missing power_supply_put()")
>
> Fixes tag
>
> Fixes: 688ea049233 ("power: supply: cpcap-charger: Allow changing constant charge voltage")
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Maybe you meant
>
> Fixes: 5688ea049233 ("power: supply: cpcap-charger: Allow changing constant charge voltage")
Thanks for the report. I fixed up the Fixes tags using your
recommendations. Obviously Tony had a problem with copying
the first character of the shortened hash :)
-- Sebastian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-01-14 22:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 22:23 linux-next: Fixes tags need some work in the battery tree Stephen Rothwell
2021-01-14 22:47 ` Sebastian Reichel [this message]
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=20210114224752.4ohn7zmrcyde474n@earth.universe \
--to=sre@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tony@atomide.com \
/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