From: Thierry Reding <treding@nvidia.com>
To: Valentin Rothberg <valentinrothberg@gmail.com>
Cc: <smohammed@nvidia.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: i2c: undefined option I2C_ALGO_BUSCLEAR
Date: Wed, 16 Nov 2016 16:39:58 +0100 [thread overview]
Message-ID: <20161116153957.GA7646@ulmo.ba.sec> (raw)
In-Reply-To: <CAD3Xx4+ieNPqsumoXuiTtpwxct-66ipJB8tb-Kfpe1njBc+OZQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 790 bytes --]
On Wed, Nov 16, 2016 at 08:31:35AM +0100, Valentin Rothberg wrote:
> Hi Shardar,
>
> your commit c3ca951fe41a ("i2c: Add Tegra BPMP I2C proxy driver")
> popped up in today's linux-next tree, adding Kconfig option
> I2C_TEGRA_BPMP, which further selects I2C_ALGO_BUSCLEAR, which is
> nowhere defined in Kconfig.
>
> Is there a patch queued somewhere to add I2C_ALGO_BUSCLEAR to Kconfig?
> I could not find anything on the lkml; only some older repositories
> on github, where the options is defined in drivers/i2c/busses/Kconfig.
This looks to be something that was part of some downstream kernel a
long time ago. Given that it doesn't exist upstream and the driver does
not use anything related to it, I'll just drop the select. Thanks for
pointing this out.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2016-11-16 15:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 7:31 i2c: undefined option I2C_ALGO_BUSCLEAR Valentin Rothberg
2016-11-16 15:39 ` Thierry Reding [this message]
2016-11-16 15:43 ` Thierry Reding
2016-11-17 8:40 ` Shardar Mohammed
2016-11-17 8:58 ` Paul Bolle
2016-11-17 11:33 ` Valentin Rothberg
2016-11-17 11:55 ` Paul Bolle
2016-11-17 12:44 ` Valentin Rothberg
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=20161116153957.GA7646@ulmo.ba.sec \
--to=treding@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=smohammed@nvidia.com \
--cc=valentinrothberg@gmail.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).