From: Sasha Levin <sashal@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Sangbeom Kim <sbkim73@samsung.com>,
Georg Waibel <georg.waibel@sensor-technik.de>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] regulator: s2mps11: Fix ERR_PTR dereference on GPIO lookup failure
Date: Mon, 24 Jun 2019 06:11:29 -0400 [thread overview]
Message-ID: <20190624101129.GQ2226@sasha-vm> (raw)
In-Reply-To: <CAJKOXPeZH+jiXxsm_cpWsfuju=vhAd2GDoj_aH811pv17C6YOQ@mail.gmail.com>
On Mon, Jun 24, 2019 at 09:01:27AM +0200, Krzysztof Kozlowski wrote:
>On Sat, 22 Jun 2019 at 20:13, Sasha Levin <sashal@kernel.org> wrote:
>>
>> Hi,
>>
>> [This is an automated email]
>>
>> This commit has been processed because it contains a "Fixes:" tag,
>> fixing commit: 1c984942f0a4 regulator: s2mps11: Pass descriptor instead of GPIO number.
>>
>> The bot has tested the following trees: v5.1.12, v4.19.53.
>>
>> v5.1.12: Build OK!
>> v4.19.53: Failed to apply! Possible dependencies:
>> Unable to calculate
>>
>>
>> How should we proceed with this patch?
>
>The commit mentioned in fixes tag (1c984942f0a4) came in
>v5.0-rc1/v5.0. Why do you try to port it to v4.19?
This is an interesting one! Usually when something like this happens, it
means that the "fixed" commit was backported to stable, but as you
pointed out, it was not.
My scripts have logic to try and detect these backports, and it appears
that there's a commit with an identical subject line in the 4.19 tree,
so at this point there are two commits with identical subject lines in
Linus's tree:
1c984942f0a4 regulator: s2mps11: Pass descriptor instead of GPIO number
0369e02b75e6 regulator: s2mps11: Pass descriptor instead of GPIO number
Which can be confusing for humans too :)
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-06-24 10:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 12:42 [PATCH] regulator: s2mps11: Fix ERR_PTR dereference on GPIO lookup failure Krzysztof Kozlowski
2019-06-20 13:32 ` Applied "regulator: s2mps11: Fix ERR_PTR dereference on GPIO lookup failure" to the regulator tree Mark Brown
2019-06-20 13:32 ` Mark Brown
[not found] ` <20190622181347.3BFC52070B@mail.kernel.org>
2019-06-24 7:01 ` [PATCH] regulator: s2mps11: Fix ERR_PTR dereference on GPIO lookup failure Krzysztof Kozlowski
2019-06-24 10:11 ` Sasha Levin [this message]
2019-06-24 10:41 ` Krzysztof Kozlowski
2019-06-24 10:47 ` Krzysztof Kozlowski
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=20190624101129.GQ2226@sasha-vm \
--to=sashal@kernel.org \
--cc=georg.waibel@sensor-technik.de \
--cc=krzk@kernel.org \
--cc=sbkim73@samsung.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.