From: Pavel Machek <pavel@denx.de>
To: Eugeniu Rosca <erosca@de.adit-jv.com>
Cc: Pavel Machek <pavel@denx.de>,
stable@kernel.org, kernel list <linux-kernel@vger.kernel.org>,
gregkh@duo.ucw.cz, roscaeugeniu@gmail.com,
stern@rowland.harvard.edu, qais.yousef@arm.com,
linux@prisktech.co.nz, mathias.nyman@intel.com, oneukum@suse.de,
linux-usb@vger.kernel.org
Subject: Re: hibernation reverts in 4.19.134: better alternative?
Date: Tue, 21 Jul 2020 13:27:40 +0200 [thread overview]
Message-ID: <20200721112740.GA17778@duo.ucw.cz> (raw)
In-Reply-To: <20200721065054.GA8290@lxhi-065.adit-jv.com>
[-- Attachment #1: Type: text/plain, Size: 2283 bytes --]
Hi!
> On Mon, Jul 20, 2020 at 12:15:22PM +0200, Pavel Machek wrote:
> > This is queued for 4.19.134-stable, reverting 3 patches. But it seems
> > better alternative is available...
> >
> > commit f3e697b7b6f5e2c570226f8f8692fb7db57215ec
> > Author: Sasha Levin <sashal@kernel.org>
> > Date: Fri Jul 17 12:58:32 2020 -0400
> >
> > Revert "usb/ohci-platform: Fix a warning when hibernating"
> >
> > This reverts commit c83258a757687ffccce37ed73dba56cc6d4b8a1b.
> >
> > Eugeniu Rosca writes:
> >
> > ...
> >
> > > - Backporting 987351e1ea7772 ("phy: core: Add consumer device
> > > link support") to v4.14.187 looks challenging enough, so probably not
> > > worth it. Anybody to contradict this?
> >
> > Backporting 987351e1ea7772 to 4.4 may be "interesting", but backport
>
> Typo? 4.14 meant?
4.4 meant. I care about 4.4 and 4.19.
> > to 4.19 seems trivial, here, and it seems to work ok according to CIP
> > test suites:
> >
> > https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/168487477
> >
> > (You can simply apply 987351e1ea7772 ignoring one file that is not yet
> > present in 4.19.)
>
> Technically yes. Backporting 987351e1ea7772 to v4.19.x avoids the panic.
> But it means integrating a v5.6 feature (isn't 987351e1ea7772 one?) into
> the v4.19.x stable tree. Isn't v4.19.x (just like any other stable
> branch) supposed to contain just fixes?
Well, backport might be preffered to reverting 3 patches that will
re-introduce WARN()s. Yes, documentation does not match reality here.
> Should then any missing prerequisite features be pumped in into the
> stable tree, whenever backporting a bugfix produces unexpected results?
>
> FWIW I confirm that:
> * setup [A] leads to the issue reported in [C]
> * setup [B] resolves the issue reported in [C]
Thank you!
> [A] v4.19 + 16bdc04cc98 + 1cb3b0095c3 + 79112cc3c29f
> [B] v4.19 + 16bdc04cc98 + 1cb3b0095c3 + 79112cc3c29f + 987351e1ea7
> [C] https://lore.kernel.org/linux-usb/20200709070023.GA18414@lxhi-065.adit-jv.com/
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2020-07-21 11:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 10:15 Pavel Machek
2020-07-21 6:50 ` Eugeniu Rosca
2020-07-21 11:27 ` Pavel Machek [this message]
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=20200721112740.GA17778@duo.ucw.cz \
--to=pavel@denx.de \
--cc=erosca@de.adit-jv.com \
--cc=gregkh@duo.ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@prisktech.co.nz \
--cc=mathias.nyman@intel.com \
--cc=oneukum@suse.de \
--cc=qais.yousef@arm.com \
--cc=roscaeugeniu@gmail.com \
--cc=stable@kernel.org \
--cc=stern@rowland.harvard.edu \
/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®