From: Sasha Levin <sashal@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Wolfram Sang <wsa@the-dreams.de>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
Maximilian Luz <luzmaximilian@gmail.com>,
stable@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH 5.8+ regression fix 0/1] i2c: core: Restore acpi_walk_dep_device_list() getting called after registering the ACPI i2c devs
Date: Thu, 15 Oct 2020 11:17:57 -0400 [thread overview]
Message-ID: <20201015151757.GS2415204@sasha-vm> (raw)
In-Reply-To: <20201014144158.18036-1-hdegoede@redhat.com>
On Wed, Oct 14, 2020 at 04:41:57PM +0200, Hans de Goede wrote:
>Wolfram, can we get this queued up to go to Linus
>soonish ?
>
>Greg, in essence this is a partial revert of the trouble
>some commit. With the 2 combined acpi_walk_dep_device_list()
>is called last again, while still doing the
>acpi_install_address_space_handler() call earlier.
>
>Since this is a somewhat nasty regression and since the poor
>timing wrt the merge-window, I was hoping that you would be
>willing to make an exception and pick up this fix before
>it hits Linus' tree?
I don't think the merge window plays any role here: this fix can go into
Linus's tree immediately and once it's there we can pick it up for
-stable right away.
--
Thanks,
Sasha
prev parent reply other threads:[~2020-10-15 15:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 14:41 [PATCH 5.8+ regression fix 0/1] i2c: core: Restore acpi_walk_dep_device_list() getting called after registering the ACPI i2c devs Hans de Goede
2020-10-14 14:41 ` [PATCH 5.8+ regression fix] " Hans de Goede
2020-10-25 12:21 ` Wolfram Sang
2020-10-14 15:13 ` [PATCH 5.8+ regression fix 0/1] " Greg Kroah-Hartman
2020-10-15 15:17 ` Sasha Levin [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=20201015151757.GS2415204@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=luzmaximilian@gmail.com \
--cc=mika.westerberg@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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).