From: Hans de Goede <hdegoede@redhat.com>
To: "Thomas Weißschuh" <linux@weissschuh.net>,
"Henrique de Moraes Holschuh" <hmh@hmh.eng.br>,
"Mark Gross" <markgross@kernel.org>
Cc: ibm-acpi-devel@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] platform/x86: thinkpad_acpi: lockdep support
Date: Wed, 12 Jul 2023 17:49:12 +0200 [thread overview]
Message-ID: <af2be377-ff04-3b00-62c7-a1ff53dddd16@redhat.com> (raw)
In-Reply-To: <20230704-thinkpad_acpi-lockdep-v1-0-60129548a738@weissschuh.net>
Hi,
On 7/4/23 23:03, Thomas Weißschuh wrote:
> Validate locking requirements in thinkpad_acpi through lockdep.
>
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
Thank you for your patch-series, I've applied the series to my
review-hans branch:
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=review-hans
Note it will show up in my review-hans branch once I've pushed my
local branch there, which might take a while.
Once I've run some tests on this branch the patches there will be
added to the platform-drivers-x86/for-next branch and eventually
will be included in the pdx86 pull-request to Linus for the next
merge-window.
Regards,
Hans
> ---
> Thomas Weißschuh (2):
> platform/x86: thinkpad_acpi: take mutex for hotkey_mask_{set,get}
> platform/x86: thinkpad_acpi: use lockdep annotations
>
> drivers/platform/x86/thinkpad_acpi.c | 45 ++++++++++++++++++++++--------------
> 1 file changed, 28 insertions(+), 17 deletions(-)
> ---
> base-commit: 03275585cabd0240944f19f33d7584a1b099a3a8
> change-id: 20230704-thinkpad_acpi-lockdep-7def9d7f91b5
>
> Best regards,
prev parent reply other threads:[~2023-07-12 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 21:03 Thomas Weißschuh
2023-07-04 21:03 ` [PATCH 1/2] platform/x86: thinkpad_acpi: take mutex for hotkey_mask_{set,get} Thomas Weißschuh
2023-07-04 21:03 ` [PATCH 2/2] platform/x86: thinkpad_acpi: use lockdep annotations Thomas Weißschuh
2023-07-12 15:49 ` Hans de Goede [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=af2be377-ff04-3b00-62c7-a1ff53dddd16@redhat.com \
--to=hdegoede@redhat.com \
--cc=hmh@hmh.eng.br \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=markgross@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
all inboxes | Powered by JetHome®