lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 7 Nov 2022 11:36:07 -0700 From: Raul Rangel <rrangel@...omium.org> To: "Rafael J. Wysocki" <rafael@...nel.org> Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>, Andy Shevchenko <andriy.shevchenko@...ux.intel.com>, ACPI Devel Maling List <linux-acpi@...r.kernel.org>, linux-input <linux-input@...r.kernel.org>, Hans de Goede <hdegoede@...hat.com>, Mika Westerberg <mika.westerberg@...ux.intel.com>, Mario Limonciello <mario.limonciello@....com>, Tim Van Patten <timvp@...gle.com>, Linus Walleij <linus.walleij@...aro.org>, "jingle.wu" <jingle.wu@....com.tw>, Dan Williams <dan.j.williams@...el.com>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Jonathan Cameron <Jonathan.Cameron@...wei.com>, Len Brown <lenb@...nel.org>, Nathan Chancellor <nathan@...nel.org>, Nick Desaulniers <ndesaulniers@...gle.com>, Terry Bowman <terry.bowman@....com>, Tom Rix <trix@...hat.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, llvm@...ts.linux.dev, Alexis Savery <asavery@...gle.com> Subject: Re: [PATCH v6 06/13] ACPI: resources: Add wake_capable parameter to acpi_dev_irq_flags On Mon, Oct 17, 2022 at 8:53 AM Raul Rangel <rrangel@...omium.org> wrote: > > On Sat, Oct 15, 2022 at 10:56 AM Rafael J. Wysocki <rafael@...nel.org> wrote: > > > > On Fri, Sep 30, 2022 at 7:55 PM Dmitry Torokhov > > <dmitry.torokhov@...il.com> wrote: > > > > > > On Fri, Sep 30, 2022 at 08:42:13PM +0300, Andy Shevchenko wrote: > > > > On Fri, Sep 30, 2022 at 07:13:37PM +0200, Rafael J. Wysocki wrote: > > > > > On Fri, Sep 30, 2022 at 1:22 AM Dmitry Torokhov > > > > > <dmitry.torokhov@...il.com> wrote: > > > > > > > > ... > > > > > > > > > I think that patches [5-8/13] from this series are significant > > > > > framework changes, so it would make sense to route them via the ACPI > > > > > tree. > > > > > > > > > > If this is fine with everybody, I will queue them up for merging into > > > > > 6.1 (probably in the second half of the upcoming merge window). > > > > > > > > I believe it's fine from GPIO ACPI perspective (there shouldn't be conflict, > > > > but if you wish you always may take this PR [1] to your tree (it's already in > > > > GPIO tree pending v6.1), it may be considered as immutable tag. > > > > > > > > [1]: https://lore.kernel.org/linux-gpio/Yym%2Fj+Y9MBOIhWtK@black.fi.intel.com/ > > > > > > Yeah, having an immutable branch hanging off 6.0-rcN would be awesome - > > > I could pull it and this would avoid any potential conflicts later. > > > > This material is in the mainline now, but the branch is still there in > > case you need it: > > > > git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \ > > acpi-wakeup > > > > It won't be necessary any more after 6.1-rc1 is out, though, I suppose. > > > Awesome, thanks for merging in the ACPI patches! Dmitry, What are the next steps to getting the I2C patches landed? Should I push out a new series that's rebased on 6.1-rc1?
Powered by blists - more mailing lists