From: Thierry Reding <treding@nvidia.com>
To: Valentin Rothberg <valentinrothberg@gmail.com>
Cc: <swarren@wwwdotorg.org>, <gnurou@gmail.com>,
<linux-kernel@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
Paul Bolle <pebolle@tiscali.nl>,
Andreas Ruprecht <andreas.ruprecht@fau.de>,
hengelein Stefan <stefan.hengelein@fau.de>
Subject: Re: soc/tegra: fuse: undefined option ARCH_TEGRA_210_SOC
Date: Fri, 15 May 2015 10:57:01 +0200 [thread overview]
Message-ID: <20150515085700.GE4984@ulmo.nvidia.com> (raw)
In-Reply-To: <CAD3Xx4+6r1w+oKgjUAuLXzszy9-uRWvXyyfv3q_1YGC6shXHFQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
On Thu, May 14, 2015 at 01:50:08PM +0200, Valentin Rothberg wrote:
> Hi Thierry,
>
> your commit e3cf5bf687df ("soc/tegra: fuse: Add Tegra210 support") is
> in today's linux-next tree (i.e., next-20150514). The following lines
> in the commit reference a Kconfig option that is not defined, so that
> the driver and the affected #ifdef blocks cannot be compiled:
>
> drivers/soc/tegra/fuse/Makefile:10:obj-$(CONFIG_ARCH_TEGRA_210_SOC)
> += speedo-tegra210.o
> drivers/soc/tegra/fuse/fuse-tegra.c:104:#ifdef CONFIG_ARCH_TEGRA_210_SOC
> drivers/soc/tegra/fuse/fuse-tegra30.c:49: defined(CONFIG_ARCH_TEGRA_210_SOC)
> drivers/soc/tegra/fuse/fuse-tegra30.c:148:#if defined(CONFIG_ARCH_TEGRA_210_SOC)
> drivers/soc/tegra/fuse/fuse.h:84:#ifdef CONFIG_ARCH_TEGRA_210_SOC
> drivers/soc/tegra/fuse/fuse.h:104:#ifdef CONFIG_ARCH_TEGRA_210_SOC
>
> Is there a patch queued somewhere to add this option?
Yes, these patches are all in the process of being merged for v4.2, so
I'd expect this particular Kconfig option to show up sometime soon now.
Thanks,
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-05-15 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 11:50 soc/tegra: fuse: undefined option ARCH_TEGRA_210_SOC Valentin Rothberg
2015-05-15 8:57 ` Thierry Reding [this message]
2015-08-21 13:24 ` 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=20150515085700.GE4984@ulmo.nvidia.com \
--to=treding@nvidia.com \
--cc=andreas.ruprecht@fau.de \
--cc=gnurou@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=stefan.hengelein@fau.de \
--cc=swarren@wwwdotorg.org \
--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