[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6a3d7b4e-7350-e52a-6139-e14eb64191ed@gmail.com>
Date: Fri, 28 Apr 2023 10:22:37 -0700
From: Doug Berger <opendmb@...il.com>
To: "Rafael J. Wysocki" <rafael@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>,
Gergo Koteles <soyer@....hu>,
Jonathan Cameron <Jonathan.Cameron@...wei.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Dan Williams <dan.j.williams@...el.com>,
Hans de Goede <hdegoede@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Kees Cook <keescook@...omium.org>,
Saravana Kannan <saravanak@...gle.com>,
Florian Fainelli <f.fainelli@...il.com>,
linux-kernel@...r.kernel.org, linux-input@...r.kernel.org
Subject: Re: [RFC PATCH 3/3] Revert "input: gpio-keys - use
device_pm_move_to_tail"
On 4/28/2023 4:40 AM, Rafael J. Wysocki wrote:
> On Fri, Apr 28, 2023 at 6:47 AM Greg Kroah-Hartman
> <gregkh@...uxfoundation.org> wrote:
>>
>> On Thu, Apr 27, 2023 at 03:16:25PM -0700, Doug Berger wrote:
>>> This reverts commit 2569873096f7eb1acf63624e9772d82b23923bf4.
>>
>> You have to give a reason why you are reverting it please...
>
> Also, the commit ID above doesn't match any commits in the mainline.
Apologies. I attempted to explain this in the cover letter, but as
anticipated it caused confusion. The relevant text was:
Both commits shouldn't really exist in the same kernel so the
third patch reverts the first in an attempt to make that clear
(though it may be a source of confusion for some).
This commit ID is the ID of the first patch of this set in my tree. It
slipped my mind that of course that wouldn't be conveyed through
send-mail :). D'oh!
To be clear, this is really a "straw man" request for comment with hope
of finding a more elegant solution to the issue.
Thanks,
Doug
Powered by blists - more mailing lists