From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH regression fix v2] gpiolib: acpi: Make set-debounce-timeout failures non fatal
Date: Tue, 21 Sep 2021 15:13:23 +0300 [thread overview]
Message-ID: <CAHp75VfhCswzUQA0veYE0OmqOitbnqYo5EnmycV2j69+0n+unw@mail.gmail.com> (raw)
In-Reply-To: <16df7a43-919b-5ad7-7ca7-025c669ba32f@redhat.com>
On Mon, Sep 20, 2021 at 7:47 PM Hans de Goede <hdegoede@redhat.com> wrote:
> On 8/16/21 2:28 PM, Hans de Goede wrote:
> > On 8/16/21 2:15 PM, Andy Shevchenko wrote:
> >> On Mon, Aug 16, 2021 at 12:41:19PM +0200, Hans de Goede wrote:
...
> >> Yes, I also think that we need to choose upper debounce instead of rejecting
> >> the settings. And yes, I agree that for now it's not suitable as a fix.
> >>
> >> That said,
> >> Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> >
> > Thank you.
> >
> > FYI, I've prepared a patch to choose the upper debounce time for
> > pintctrl-baytrail . I'll test it when I'm back home tonight and
> > then submit it upstream.
>
> Ugh, I just noticed that this is still not upstream (not in v5.15-rc2), while this is
> a regression fix!
I think it was late for Bart to pick this up.
> Can we please get this merged and send to Linus ASAP ?
I'm on vacations now, but if Mika or Bart or Linus can handle this, my
tag is there :)
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2021-09-21 12:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 10:41 [PATCH regression fix v2] gpiolib: acpi: Make set-debounce-timeout failures non fatal Hans de Goede
2021-08-16 12:15 ` Andy Shevchenko
2021-08-16 12:28 ` Hans de Goede
2021-08-23 9:41 ` Andy Shevchenko
2021-09-20 14:43 ` Hans de Goede
2021-09-21 12:13 ` Andy Shevchenko [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=CAHp75VfhCswzUQA0veYE0OmqOitbnqYo5EnmycV2j69+0n+unw@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
/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).