From: Pavel Machek <pavel@denx.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
dianders@chromium.org, grundler@chromium.org,
davem@davemloft.net
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, allen.lkml@gmail.com
Subject: RTL8152_INACCESSIBLE was Re: [PATCH 6.1 000/194] 6.1.68-rc1 review
Date: Tue, 12 Dec 2023 21:08:35 +0100 [thread overview]
Message-ID: <ZXi9wyS7vjGyUWU8@duo.ucw.cz> (raw)
In-Reply-To: <20231211182036.606660304@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1315 bytes --]
Hi!
> This is the start of the stable review cycle for the 6.1.68 release.
> There are 194 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
> Douglas Anderson <dianders@chromium.org>
> r8152: Add RTL8152_INACCESSIBLE to r8153_aldps_en()
>
> Douglas Anderson <dianders@chromium.org>
> r8152: Add RTL8152_INACCESSIBLE to r8153_pre_firmware_1()
>
> Douglas Anderson <dianders@chromium.org>
> r8152: Add RTL8152_INACCESSIBLE to r8156b_wait_loading_flash()
>
> Douglas Anderson <dianders@chromium.org>
> r8152: Add RTL8152_INACCESSIBLE checks to more loops
>
> Douglas Anderson <dianders@chromium.org>
> r8152: Rename RTL8152_UNPLUG to RTL8152_INACCESSIBLE
Central patch that actually fixes something is:
commit d9962b0d42029bcb40fe3c38bce06d1870fa4df4
Author: Douglas Anderson <dianders@chromium.org>
Date: Fri Oct 20 14:06:59 2023 -0700
r8152: Block future register access if register access fails
...but we don't have that in 6.1. So we should not need the rest,
either.
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2023-12-12 20:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 18:19 Greg Kroah-Hartman
2023-12-11 21:15 ` Florian Fainelli
2023-12-12 0:26 ` Kelsey Steele
2023-12-12 13:21 ` Naresh Kamboju
2023-12-12 14:02 ` Conor Dooley
2023-12-12 16:12 ` Shuah Khan
2023-12-12 17:34 ` Guenter Roeck
2023-12-12 19:08 ` Pavel Machek
2023-12-12 20:08 ` Pavel Machek [this message]
2023-12-12 20:48 ` RTL8152_INACCESSIBLE was " Guenter Roeck
2023-12-13 7:52 ` Pavel Machek
2023-12-13 8:50 ` Greg Kroah-Hartman
2023-12-13 15:16 ` Doug Anderson
2023-12-13 17:37 ` Greg Kroah-Hartman
2023-12-13 18:17 ` Doug Anderson
2023-12-12 21:57 ` Ron Economos
2023-12-12 22:21 ` Jon Hunter
2023-12-12 22:23 ` SeongJae Park
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=ZXi9wyS7vjGyUWU8@duo.ucw.cz \
--to=pavel@denx.de \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=conor@kernel.org \
--cc=davem@davemloft.net \
--cc=dianders@chromium.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=grundler@chromium.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®