From: Sven Van Asbroeck <thesven73@gmail.com>
To: Sasha Levin <sashal@kernel.org>
Cc: Sebastian Reichel <sre@kernel.org>,
linux-pm@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Stable <stable@vger.kernel.org>
Subject: Re: [PATCH v1] power: supply: ltc2941-battery-gauge: fix use-after-free
Date: Thu, 19 Sep 2019 14:58:12 -0400 [thread overview]
Message-ID: <CAGngYiW2bObc8L+mQJEMzYRe+QU7Xx1X_-So-o0RYAE7TWr3rg@mail.gmail.com> (raw)
In-Reply-To: <20190919182904.AF657207FC@mail.kernel.org>
On Thu, Sep 19, 2019 at 2:29 PM Sasha Levin <sashal@kernel.org> wrote:
>
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the following trees: all
>
> The bot has tested the following trees: v5.2.15, v4.19.73, v4.14.144, v4.9.193, v4.4.193.
>
> v5.2.15: Build OK!
> v4.19.73: Build OK!
> v4.14.144: Build OK!
> v4.9.193: Build OK!
> v4.4.193: Failed to apply! Possible dependencies:
> Unable to calculate
>
>
> NOTE: The patch will not be queued to stable trees until it is upstream.
>
> How should we proceed with this patch?
>
> --
> Thanks,
> Sasha
Doesn't apply on 4.4 because power supply drivers moved to a different
directory (power/supply) between 4.4 and 4.9.
I will post a patch with a fixed-up file path, marked as "[PATCH 4.4 v1]".
If this should be addressed differently, please let me know.
Sven
next prev parent reply other threads:[~2019-09-19 18:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 15:11 [PATCH v1] power: supply: ltc2941-battery-gauge: fix use-after-free Sven Van Asbroeck
[not found] ` <20190919182904.AF657207FC@mail.kernel.org>
2019-09-19 18:58 ` Sven Van Asbroeck [this message]
2019-09-19 19:02 ` [PATCH 4.4 " Sven Van Asbroeck
2019-12-02 18:43 ` Greg KH
2019-12-02 19:59 ` Sven Van Asbroeck
2020-02-07 8:51 ` Greg KH
2019-10-20 21:15 ` [PATCH " 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=CAGngYiW2bObc8L+mQJEMzYRe+QU7Xx1X_-So-o0RYAE7TWr3rg@mail.gmail.com \
--to=thesven73@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=sre@kernel.org \
--cc=stable@vger.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).