From: Philipp Zabel <p.zabel@pengutronix.de>
To: arm@kernel.org
Cc: linux-arm-kernel@lists.infradead.org, kernel@pengutronix.de
Subject: [GIT PULL RESEND] Reset controller fixes for v5.16
Date: Fri, 19 Nov 2021 18:07:14 +0100 [thread overview]
Message-ID: <5383deda141721643419e98c485fb510be56fb61.camel@pengutronix.de> (raw)
Message-ID: <20211119170714.BQFJ7tn39YCcxjxErR9lKorUx6FTJ9inZFOmDd1zR8w@z> (raw)
Dear arm-soc maintainers,
The following changes since commit fa55b7dcdc43c1aa1ba12bca9d2dd4318c2a0dbf:
Linux 5.16-rc1 (2021-11-14 13:56:52 -0800)
are available in the Git repository at:
git://git.pengutronix.de/pza/linux tags/reset-fixes-for-v5.16
for you to fetch changes up to 69125b4b9440be015783312e1b8753ec96febde0:
reset: tegra-bpmp: Revert Handle errors in BPMP response (2021-11-17 17:22:27 +0100)
----------------------------------------------------------------
Reset controller fixes for v5.16
Well, just one: revert commit c045ceb5a145 ("reset: tegra-bpmp: Handle
errors in BPMP response"), which exposed an issue with the Tegra194 HDA
controller reset. BPMP response error handling will be reinstated once
there's a fix for the HDA issue.
----------------------------------------------------------------
Jon Hunter (1):
reset: tegra-bpmp: Revert Handle errors in BPMP response
drivers/reset/tegra/reset-bpmp.c | 9 +--------
1 file changed, 1 insertion(+), 8 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-12-06 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 17:07 Philipp Zabel [this message]
2021-11-19 17:07 ` [GIT PULL RESEND] Reset controller fixes for v5.16 Philipp Zabel
2021-12-13 12:21 ` [GIT PULL] " Jon Hunter
2021-12-13 13:15 ` Arnd Bergmann
2021-12-13 13:30 ` Philipp Zabel
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=5383deda141721643419e98c485fb510be56fb61.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=arm@kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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).