From: Baolin Wang <baolin.wang@linaro.org>
To: stable@vger.kernel.org, peterz@infradead.org, mingo@redhat.com,
linus.walleij@linaro.org, natechancellor@gmail.com,
sre@kernel.org
Cc: longman@redhat.com, linux-gpio@vger.kernel.org,
david@lechnology.com, linux-pm@vger.kernel.org, arnd@arndb.de,
baolin.wang@linaro.org, orsonzhai@gmail.com,
vincent.guittot@linaro.org, linux-kernel@vger.kernel.org
Subject: [BACKPORT 4.19.y 0/3] Candidates from Spreadtrum 4.14 product kernel
Date: Wed, 25 Sep 2019 17:52:26 +0800 [thread overview]
Message-ID: <cover.1569404757.git.baolin.wang@linaro.org> (raw)
With Arnd's script [1] help, I found some bugfixes in Spreadtrum 4.14 product
kernel, but missing in v4.19.75:
513e1073d52e locking/lockdep: Add debug_locks check in __lock_downgrade()
957063c92473 pinctrl: sprd: Use define directive for sprd_pinconf_params values
87a2b65fc855 power: supply: sysfs: ratelimit property read error message
[1] https://lore.kernel.org/lkml/20190322154425.3852517-19-arnd@arndb.de/T/
David Lechner (1):
power: supply: sysfs: ratelimit property read error message
Nathan Chancellor (1):
pinctrl: sprd: Use define directive for sprd_pinconf_params values
Waiman Long (1):
locking/lockdep: Add debug_locks check in __lock_downgrade()
drivers/pinctrl/sprd/pinctrl-sprd.c | 6 ++----
drivers/power/supply/power_supply_sysfs.c | 3 ++-
kernel/locking/lockdep.c | 3 +++
3 files changed, 7 insertions(+), 5 deletions(-)
--
1.7.9.5
next reply other threads:[~2019-09-25 9:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 9:52 Baolin Wang [this message]
2019-09-25 9:55 ` [BACKPORT 4.19.y 3/3] power: supply: sysfs: ratelimit property read error message Baolin Wang
2019-09-28 20:02 ` [BACKPORT 4.19.y 0/3] Candidates from Spreadtrum 4.14 product kernel Sasha Levin
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=cover.1569404757.git.baolin.wang@linaro.org \
--to=baolin.wang@linaro.org \
--cc=arnd@arndb.de \
--cc=david@lechnology.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=natechancellor@gmail.com \
--cc=orsonzhai@gmail.com \
--cc=peterz@infradead.org \
--cc=sre@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vincent.guittot@linaro.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).