From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: corentin.chary@gmail.com, luke@ljones.dev, Armin Wolf <W_Armin@gmx.de>
Cc: hdegoede@redhat.com, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/5] platform/x86: wmi: Fixes for event data handling
Date: Mon, 19 Feb 2024 14:06:54 +0200 [thread overview]
Message-ID: <170834441476.4050.13616916099862661423.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20240219115919.16526-1-W_Armin@gmx.de>
On Mon, 19 Feb 2024 12:59:14 +0100, Armin Wolf wrote:
> This patch series contains fixes for the handling of WMI event data
> when receiving WMI events.
>
> The first patch aims to prevent WMI event drivers depending on WMI
> event data support from binding to a WMI device which does not
> support the retrieval of additional WMI event data.
>
> [...]
Thank you for your contribution, it has been applied to my local
review-ilpo branch. Note it will show up in the public
platform-drivers-x86/review-ilpo branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/5] platform/x86: wmi: Prevent incompatible event driver from probing
commit: b448bcb4cf02b27946f9bd6c4ded17e2209bf271
[2/5] platform/x86: wmi: Check if event data is not NULL
commit: b5003c979eb4128c7ca81ed144491e85232979b6
[3/5] platform/x86: wmi: Always evaluate _WED when receiving an event
commit: 2b30ea09e77d701f0b0b02243bdcf8aa408e4214
[4/5] platform/x86: wmi: Update documentation regarding _WED
commit: c865db581c295085fbfc1b6802f87c38ad92e4ca
[5/5] Revert "platform/x86: asus-wmi: Support WMI event queue"
commit: b27bb403e136b12cafeff4467d495bbc8c9b7441
--
i.
prev parent reply other threads:[~2024-02-19 12:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 11:59 Armin Wolf
2024-02-19 11:59 ` [PATCH v2 1/5] platform/x86: wmi: Prevent incompatible event driver from probing Armin Wolf
2024-02-19 11:59 ` [PATCH v2 2/5] platform/x86: wmi: Check if event data is not NULL Armin Wolf
2024-02-20 0:59 ` Armin Wolf
2024-02-20 9:19 ` Ilpo Järvinen
2024-02-21 3:21 ` Armin Wolf
2024-02-19 11:59 ` [PATCH v2 3/5] platform/x86: wmi: Always evaluate _WED when receiving an event Armin Wolf
2024-02-19 11:59 ` [PATCH v2 4/5] platform/x86: wmi: Update documentation regarding _WED Armin Wolf
2024-02-19 11:59 ` [PATCH v2 5/5] Revert "platform/x86: asus-wmi: Support WMI event queue" Armin Wolf
2024-02-19 12:06 ` Ilpo Järvinen [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=170834441476.4050.13616916099862661423.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=W_Armin@gmx.de \
--cc=corentin.chary@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@ljones.dev \
--cc=platform-driver-x86@vger.kernel.org \
/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
all inboxes | Powered by JetHome®