linux-kernel - Re: [PATCH -next] gpiolib: acpi: Use METHOD_NAME__AEI macro for acpi_walk

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Y1FSRJC9s+7cvJI3@smile.fi.intel.com>
Date:   Thu, 20 Oct 2022 16:51:00 +0300
From:   Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:     Bartosz Golaszewski <brgl@...ev.pl>
Cc:     Xiang Yang <xiangyang3@...wei.com>,
        mika.westerberg@...ux.intel.com, linus.walleij@...aro.org,
        linux-gpio@...r.kernel.org, linux-acpi@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH -next] gpiolib: acpi: Use METHOD_NAME__AEI macro for
 acpi_walk_resources

On Thu, Oct 20, 2022 at 03:23:27PM +0200, Bartosz Golaszewski wrote:
> On Thu, Oct 20, 2022 at 3:48 AM Xiang Yang <xiangyang3@...wei.com> wrote:
> >
> > Using the METHOD_NAME__AEI macro instead of using "_AEI" directly.
> >
> > Signed-off-by: Xiang Yang <xiangyang3@...wei.com>
> > ---
> >  drivers/gpio/gpiolib-acpi.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpio/gpiolib-acpi.c b/drivers/gpio/gpiolib-acpi.c
> > index a7d2358736fe..064ba5150fd4 100644
> > --- a/drivers/gpio/gpiolib-acpi.c
> > +++ b/drivers/gpio/gpiolib-acpi.c
> > @@ -512,7 +512,7 @@ void acpi_gpiochip_request_interrupts(struct gpio_chip *chip)
> >         if (ACPI_FAILURE(status))
> >                 return;
> >
> > -       acpi_walk_resources(handle, "_AEI",
> > +       acpi_walk_resources(handle, METHOD_NAME__AEI,
> >                             acpi_gpiochip_alloc_event, acpi_gpio);
> 
> This line dates back to 2018 so why -next in your PATCH tag?

This means "for Linux next cycle". It has roots in the net subsystem where
it's a requirement to mark each patch either net or net-next, because they
have a huge traffic of patches.

> That being said - patch applied (unless Andy wants to take it directly).

I think I will take it. Care to provide your tag?

-- 
With Best Regards,
Andy Shevchenko