[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bzb6rk7q7rs27kbonihpfftkgueievpux7vpqjgrgsud5pf5g2@tuxymj7vk3it>
Date: Tue, 25 Mar 2025 18:29:44 +0100
From: Benjamin Tissoires <bentiss@...nel.org>
To: Aditya Garg <adityagarg1208@...il.com>
Cc: admin@...eit.net, benjamin.tissoires@...hat.com, gargaditya08@...e.com,
jikos@...nel.org, jkosina@...e.com, kekrby@...il.com, linux-input@...r.kernel.org,
linux-kernel@...r.kernel.org, orlandoch.dev@...il.com
Subject: Re: [PATCH RESEND 5/5] HID: multitouch: add device ID for Apple
Touch Bar
On Mar 25 2025, Aditya Garg wrote:
> Yes I can move hid_find_field to the original location as well. But, I would not want to devm_kzalloc as well unnecessarily if the touchbar is in the basic mode instead of drm mode which will cause this -ENODEV to be executed right?
It shouldn't matter. hid_core calls devres_open_group() before calling
.probe(), and calls devres_release_group() on failure. So yes, we'll
allocate a piece of memory and release it after, but it's not something
uncommon.
Cheers,
Benjamin
Powered by blists - more mailing lists