linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Sebastian Reichel <sre@kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Michael Nosthoff <committed@heine.so>
Subject: linux-next: Fixes tag needs some work in the battery tree
Date: Mon, 2 Sep 2019 09:31:31 +1000	[thread overview]
Message-ID: <20190902093131.06f66c9f@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 710 bytes --]

Hi all,

In commit

  b19aca4eb2d2 ("power: supply: sbs-battery: only return health when battery present")

Fixes tag

  Fixes: 76b16f4cdfb8 ("power: supply: sbs-battery: don't assume

has these problem(s):

  - Subject has leading but no trailing parentheses
  - Subject has leading but no trailing quotes

In commit

  38fa8b9f75ea ("power: supply: sbs-battery: use correct flags field")

Fixes tag

  Fixes: 76b16f4cdfb8 ("power: supply: sbs-battery: don't assume

has these problem(s):

  - Subject has leading but no trailing parentheses
  - Subject has leading but no trailing quotes

Please do not split Fixes tags over more than one line.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2019-09-01 23:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-01 23:31 Stephen Rothwell [this message]
2019-09-02  7:10 ` linux-next: Fixes tag needs some work in the battery tree Sebastian Reichel
2019-09-02  7:32   ` Michael Nosthoff
2019-09-02  8:25     ` Sebastian Reichel
2020-01-15 19:56 Stephen Rothwell
2020-10-05 11:50 Stephen Rothwell
2020-10-06  3:57 ` Ikjoon Jang
2020-10-06  4:18   ` Ikjoon Jang
2021-01-14 19:39 Stephen Rothwell
2021-01-14 22:45 ` Sebastian Reichel

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=20190902093131.06f66c9f@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=committed@heine.so \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sre@kernel.org \
    /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).