From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Jul 22
Date: Fri, 22 Jul 2016 20:54:26 -0400 [thread overview]
Message-ID: <CAP=VYLrEJGEBG=OiZUwxVA0ujn9OWECRr-X=cz+c+=06Fqz0PA@mail.gmail.com> (raw)
In-Reply-To: <CAP=VYLrkNuvwL0T=0ot_3Wk_VpSzdiJ-ZTcGA71D1od6dQRzAg@mail.gmail.com>
On Fri, Jul 22, 2016 at 3:28 PM, Paul Gortmaker
<paul.gortmaker@windriver.com> wrote:
[...]
>
> For x86-64 allmod, I am seeing this issue for the 1st time today
> in my local builds, even though it doesn't appear in sfr's builds:
>
> FATAL: drivers/input/evbug: sizeof(struct input_device_id)=312 is not
> a modulo of the size of section
> __mod_input__<identifier>_device_table=384.
> Fix definition of struct input_device_id in mod_devicetable.h
> make[2]: *** [__modpost] Error 1
> make[1]: *** [modules] Error 2
> make: *** [sub-make] Error 2
>
> paul@builder:~/git/linux-head$ git describe
> next-20160722
>
> Nothing has touched drivers/input/evbug.c for years...
Circling back to look at this more, it seems to be a result of the
makefiles not clobbering something properly when using the
same build directory from yesterday's next build today.
Once I executed a "make clean" I could not reproduce it.
P.
--
next prev parent reply other threads:[~2016-07-23 0:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 7:10 linux-next: Tree for Jul 22 Stephen Rothwell
2016-07-22 19:28 ` Paul Gortmaker
2016-07-23 0:54 ` Paul Gortmaker [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-22 10:43 Stephen Rothwell
2021-07-22 6:42 Stephen Rothwell
2020-07-22 13:16 Stephen Rothwell
2019-07-22 3:59 Stephen Rothwell
2015-07-22 5:25 Stephen Rothwell
2013-07-22 4:04 Stephen Rothwell
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='CAP=VYLrEJGEBG=OiZUwxVA0ujn9OWECRr-X=cz+c+=06Fqz0PA@mail.gmail.com' \
--to=paul.gortmaker@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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).