From: Shardar Mohammed <smohammed@nvidia.com>
To: Thierry Reding <treding@nvidia.com>,
Valentin Rothberg <valentinrothberg@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: RE: i2c: undefined option I2C_ALGO_BUSCLEAR
Date: Thu, 17 Nov 2016 08:40:34 +0000 [thread overview]
Message-ID: <14d6032a790e416194159e3ebb43f001@bgmail102.nvidia.com> (raw)
In-Reply-To: <20161116154327.GB7646@ulmo.ba.sec>
> On Wed, Nov 16, 2016 at 04:39:57PM +0100, Thierry Reding wrote:
> > 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.
>
> Actually the I2C_ALGO_BIT seems to be completely unused as well. I'm going
> to drop that, too.
>
Yes as Thierry mentioned both I2C_ALGO_BUSCLEAR and I2C_ALGO_BIT can be removed as these are obsolete.
next prev parent reply other threads:[~2016-11-17 8: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
2016-11-16 15:43 ` Thierry Reding
2016-11-17 8:40 ` Shardar Mohammed [this message]
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=14d6032a790e416194159e3ebb43f001@bgmail102.nvidia.com \
--to=smohammed@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=treding@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).