From: Dmitry Torokhov <dtor@vmware.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the rr tree
Date: Wed, 9 Feb 2011 00:36:35 -0800 [thread overview]
Message-ID: <20110209083634.GA29918@dtor-ws.eng.vmware.com> (raw)
In-Reply-To: <201102091243.46227.rusty@rustcorp.com.au>
On Tue, Feb 08, 2011 at 06:13:46PM -0800, Rusty Russell wrote:
> On Wed, 9 Feb 2011 12:31:15 pm Stephen Rothwell wrote:
> > Hi Rusty,
> >
> > After merging the rr tree, today's linux-next build (powerpc
> > ppc64_defconfig) failed like this:
> >
> > drivers/net/myri10ge/myri10ge.c: In function 'myri10ge_select_firmware':
> > drivers/net/myri10ge/myri10ge.c:3341: error: request for member 'perm' in something not a structure or union
> > drivers/net/myri10ge/myri10ge.c:3341: error: request for member 'perm' in something not a structure or union
> > drivers/net/myri10ge/myri10ge.c:3341: error: request for member 'perm' in something not a structure or union
> > drivers/net/myri10ge/myri10ge.c:3349: error: request for member 'perm' in something not a structure or union
> > drivers/net/myri10ge/myri10ge.c:3349: error: request for member 'perm' in something not a structure or union
> > drivers/net/myri10ge/myri10ge.c:3349: error: request for member 'perm' in something not a structure or union
> >
> > Caused by commit b3e402b450f954d0a8ec04e05433654d4a9df2a6 ("module: deal
> > with alignment issues in built-in module parameters") so I have used the
> > rr tree from next-20110208 for today.
>
> Thanks! Fix is obvious, I will write it now...
>
Sorry about this. None of the drivers using kparam_block_sysfs_write()
happened to be enabled in my .config.
Thanks,
Dmitry
next prev parent reply other threads:[~2011-02-09 8:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 2:01 linux-next: build failure after merge of the rr tree Stephen Rothwell
2011-02-09 2:13 ` Rusty Russell
2011-02-09 8:36 ` Dmitry Torokhov [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-20 2:39 Stephen Rothwell
2011-12-20 3:54 ` Rusty Russell
2011-08-30 4:03 Stephen Rothwell
2011-08-31 4:36 ` Rusty Russell
2011-01-19 4:42 Stephen Rothwell
2011-01-19 9:59 ` Rusty Russell
2011-01-19 10:05 ` Linus Walleij
2011-01-19 10:04 ` Linus Walleij
2010-08-04 2:15 Stephen Rothwell
2010-06-02 2:03 Stephen Rothwell
2010-06-02 4:45 ` Rusty Russell
2010-06-01 3:11 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=20110209083634.GA29918@dtor-ws.eng.vmware.com \
--to=dtor@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--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