linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Nosthoff" <michael@nosthoff.rocks>
To: "Sebastian Reichel" <sre@kernel.org>
Cc: "Stephen Rothwell" <sfr@canb.auug.org.au>,
	"Linux Next Mailing List" <linux-next@vger.kernel.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in  the battery tree
Date: Mon, 02 Sep 2019 09:32:47 +0200	[thread overview]
Message-ID: <79b6-5d6cc580-3-35015040@57153312> (raw)
In-Reply-To: <20190902071041.ukvc64tg5tjttk6w@earth.universe>

Hi Sebastian,

I think you missed that the second commit

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

also needs this fix.


Regards,
Michael

On Monday, September 02, 2019 09:10 CEST, Sebastian Reichel <sre@kernel.org> wrote:

> Hi Stephen,
>
> On Mon, Sep 02, 2019 at 09:31:31AM +1000, Stephen Rothwell wrote:
> > In commit
> >
> > b19aca4eb2d2 ("power: supply: sbs-battery: only return health when battery present")
> >
> > [...]
> >
> > Please do not split Fixes tags over more than one line.
>
> I have fixed this and rebased the branch, so the issue should be
> gone tomororw. Thanks for the notice,
>
> -- Sebastian


  reply	other threads:[~2019-09-02  7:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-01 23:31 linux-next: Fixes tag needs some work in the battery tree Stephen Rothwell
2019-09-02  7:10 ` Sebastian Reichel
2019-09-02  7:32   ` Michael Nosthoff [this message]
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=79b6-5d6cc580-3-35015040@57153312 \
    --to=michael@nosthoff.rocks \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --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).