From: patchwork-bot+bluetooth@kernel.org
To: Arnd Bergmann <arnd@kernel.org>
Cc: jikos@kernel.org, bentiss@kernel.org,
srinivas.pandruvada@linux.intel.com, mpearson-lenovo@squebb.ca,
arnd@arndb.de, basavaraj.natikar@amd.com, even.xu@intel.com,
xinpeng.sun@intel.com, luzmaximilian@gmail.com,
marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, dmitry.torokhov@gmail.com,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org, linux-usb@vger.kernel.org,
linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] hid: intel-thc: fix CONFIG_HID dependency
Date: Thu, 20 Feb 2025 18:31:54 +0000 [thread overview]
Message-ID: <174007631401.1417233.14540583372854918839.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250123134908.805346-1-arnd@kernel.org>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Jiri Kosina <jkosina@suse.com>:
On Thu, 23 Jan 2025 14:48:12 +0100 you wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> In drivers/hid/, most drivers depend on CONFIG_HID, while a couple of the
> drivers in subdirectories instead depend on CONFIG_HID_SUPPORT and use
> 'select HID'. With the newly added INTEL_THC_HID, this causes a build
> warning for a circular dependency:
>
> [...]
Here is the summary with links:
- hid: intel-thc: fix CONFIG_HID dependency
https://git.kernel.org/bluetooth/bluetooth-next/c/a5a056c8d2ba
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-02-20 18:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 13:48 [PATCH] hid: intel-thc: fix CONFIG_HID dependency Arnd Bergmann
2025-01-24 12:20 ` Ilpo Järvinen
2025-01-25 16:35 ` Maximilian Luz
2025-01-26 1:10 ` Xu, Even
2025-02-03 9:56 ` Jiri Kosina
2025-02-20 18:31 ` patchwork-bot+bluetooth [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=174007631401.1417233.14540583372854918839.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=basavaraj.natikar@amd.com \
--cc=bentiss@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=even.xu@intel.com \
--cc=jikos@kernel.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=luzmaximilian@gmail.com \
--cc=marcel@holtmann.org \
--cc=mpearson-lenovo@squebb.ca \
--cc=platform-driver-x86@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=xinpeng.sun@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 NNTP newsgroup(s).