From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Raag Jadav <raag.jadav@intel.com>
Cc: rafael@kernel.org, lenb@kernel.org, robert.moore@intel.com,
mika.westerberg@linux.intel.com,
andriy.shevchenko@linux.intel.com,
stanislaw.gruszka@linux.intel.com, linux-acpi@vger.kernel.org,
acpica-devel@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] ACPI: bus: allow _UID matching for integer zero
Date: Wed, 10 Apr 2024 15:31:01 +0200 [thread overview]
Message-ID: <CAJZ5v0idPeRmx1oRHoVEZYmGm1D-5SFP9_C0Bu_fiuyf7YiYqQ@mail.gmail.com> (raw)
In-Reply-To: <ZhYq_HDwAi4B49Zz@black.fi.intel.com>
On Wed, Apr 10, 2024 at 8:00 AM Raag Jadav <raag.jadav@intel.com> wrote:
>
> On Thu, Mar 28, 2024 at 09:25:40AM +0530, Raag Jadav wrote:
> > Commit b2b32a173881 ("ACPI: bus: update acpi_dev_hid_uid_match() to
> > support multiple types") added _UID matching support for both integer
> > and string types, which satisfies NULL @uid2 argument for string types
> > using inversion, but this logic prevents _UID comparision in case the
> > argument is integer 0, which may result in false positives.
> >
> > Fix this using _Generic(), which will allow NULL @uid2 argument for
> > string types as well as _UID matching for all possible integer values.
> >
> > Fixes: b2b32a173881 ("ACPI: bus: update acpi_dev_hid_uid_match() to support multiple types")
> > Signed-off-by: Raag Jadav <raag.jadav@intel.com>
>
> Bump.
>
> Anything I can do to move this forward?
Should be there in linux-next already, isn't it?
Maybe I forgot to send an "applied" message.
next prev parent reply other threads:[~2024-04-10 13:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 3:55 [PATCH v1] ACPI: bus: allow _UID matching for integer zero Raag Jadav
2024-04-10 6:00 ` Raag Jadav
2024-04-10 13:31 ` Rafael J. Wysocki [this message]
2024-04-10 7:49 ` Mika Westerberg
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=CAJZ5v0idPeRmx1oRHoVEZYmGm1D-5SFP9_C0Bu_fiuyf7YiYqQ@mail.gmail.com \
--to=rafael@kernel.org \
--cc=acpica-devel@lists.linux.dev \
--cc=andriy.shevchenko@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=raag.jadav@intel.com \
--cc=robert.moore@intel.com \
--cc=stanislaw.gruszka@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 read-only IMAP folder(s) and NNTP newsgroup(s).