From: Wolfram Sang <wsa@kernel.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Eddie James <eajames@linux.ibm.com>,
linux-input@vger.kernel.org
Subject: Re: linux-next: Tree for Aug 15 (input/misc/ibm-panel.c)
Date: Tue, 16 Aug 2022 08:03:25 +0200 [thread overview]
Message-ID: <YvszHpWoIT37lcoD@shikoro> (raw)
In-Reply-To: <YvsaCjnkucMeyj60@google.com>
[-- Attachment #1: Type: text/plain, Size: 122 bytes --]
> It sounds like I need to adjust the depend statement to be:
>
> depends on I2C && I2C_SLAVE
Yes.
Thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-08-16 8:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 2:29 linux-next: Tree for Aug 15 Stephen Rothwell
2022-08-16 1:26 ` linux-next: Tree for Aug 15 (input/misc/ibm-panel.c) Randy Dunlap
2022-08-16 4:16 ` Dmitry Torokhov
2022-08-16 6:03 ` Wolfram Sang [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=YvszHpWoIT37lcoD@shikoro \
--to=wsa@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=eajames@linux.ibm.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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).