From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>, Armin Wolf <W_Armin@gmx.de>
Cc: corbet@lwn.net, platform-driver-x86@vger.kernel.org,
linux-doc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] platform/x86: wmi: Update WMI driver API documentation
Date: Wed, 9 Oct 2024 12:08:30 +0300 (EEST) [thread overview]
Message-ID: <14abcee7-29b2-bb8c-c2b7-02a397db10b2@linux.intel.com> (raw)
In-Reply-To: <263ec855-d19d-4b81-b3cd-1a7f575c9c27@redhat.com>
On Sun, 6 Oct 2024, Hans de Goede wrote:
> Hi Armin,
>
> On 5-Oct-24 11:38 PM, Armin Wolf wrote:
> > The WMI driver core now passes the WMI event data to legacy notify
> > handlers, so WMI devices sharing notification IDs are now being
> > handled properly.
> >
> > Fixes: e04e2b760ddb ("platform/x86: wmi: Pass event data directly to legacy notify handlers")
> > Signed-off-by: Armin Wolf <W_Armin@gmx.de>
>
> Thank you for your patch/series, I've applied this patch
> (series) to my review-hans branch:
> https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=review-hans
>
> I will include this patch in my next fixes pull-req to Linus
> for the current kernel development cycle.
>
> Since patch 2/2 makes non pure bugfix functional changes
> I expect Ilpo to pick that one up for pdx86/for-next.
Patch 2/2 is now in review-ilpo branch.
--
i.
prev parent reply other threads:[~2024-10-09 9:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-05 21:38 [PATCH 1/2] platform/x86: wmi: Update WMI driver API documentation Armin Wolf
2024-10-05 21:38 ` [PATCH 2/2] platform/x86: wmi: Implement proper shutdown handling Armin Wolf
2024-10-06 10:49 ` [PATCH 1/2] platform/x86: wmi: Update WMI driver API documentation Hans de Goede
2024-10-09 9:08 ` 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=14abcee7-29b2-bb8c-c2b7-02a397db10b2@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=W_Armin@gmx.de \
--cc=corbet@lwn.net \
--cc=hdegoede@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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