From: treding@nvidia.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-next] compile fail with "soc/tegra: fuse: Unify Tegra20 and Tegra30 drivers"
Date: Thu, 4 Jun 2015 10:49:03 +0200 [thread overview]
Message-ID: <20150604084902.GL29060@ulmo.nvidia.com> (raw)
In-Reply-To: <20150603160808.GM29898@windriver.com>
On Wed, Jun 03, 2015 at 12:08:08PM -0400, Paul Gortmaker wrote:
> Hi Thierry,
>
> This commit:
>
> commit 436b6428b9cc97f61721f335eb9d8010751a337e
> Author: Thierry Reding <treding@nvidia.com>
> Date: Wed Apr 29 16:54:04 2015 +0200
>
> soc/tegra: fuse: Unify Tegra20 and Tegra30 drivers
>
> in linux-next, in combination with my pending init cleanup
>
> http://marc.info/?l=linux-kernel&m=143327626201054&w=2
>
> will cause a compile fail because 43b642 is relying on an
> implicit include of <linux/module.h> to provide the fcn for:
>
> +module_platform_driver(tegra_fuse_driver);
>
> which in turn causes:
>
> drivers/soc/tegra/fuse/fuse-tegra.c:171:1: error: type defaults to 'int' in declaration of 'module_init' [-Werror=implicit-int]
> drivers/soc/tegra/fuse/fuse-tegra.c:171:1: error: type defaults to 'int' in declaration of 'module_exit' [-Werror=implicit-int]
>
> Can you add the include to your tree please? I think it makes
> more sense to be there vs. me preemptively adding it to mine.
I've squashed a patch from Paul Walmsley into the offending commit and
pushed a new for-next branch of the Tegra tree, so this should be fixed
in the next iteration.
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150604/8f9f61e4/attachment.sig>
prev parent reply other threads:[~2015-06-04 8:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 16:08 [linux-next] compile fail with "soc/tegra: fuse: Unify Tegra20 and Tegra30 drivers" Paul Gortmaker
2015-06-04 8:49 ` Thierry Reding [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=20150604084902.GL29060@ulmo.nvidia.com \
--to=treding@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).