From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Gleb Natapov <gleb@redhat.com>, Netdev <netdev@vger.kernel.org>
Subject: Re: linux-next: Tree for Jan 25 (net/sock.h, jump_label, memcg)
Date: Thu, 26 Jan 2012 18:18:28 +0100 [thread overview]
Message-ID: <CAMuHMdWp1wEHqPXNs+kaMYpomJnfbZPJjRk5GVFCuCL4Q5zK7g@mail.gmail.com> (raw)
In-Reply-To: <4F2052DB.4060602@xenotime.net>
On Wed, Jan 25, 2012 at 20:07, Randy Dunlap <rdunlap@xenotime.net> wrote:
> back to net/sock.h and jump_label:
>
> (on i386:)
>
> /next/linux-next-20120125/include/net/sock.h:953:2: error: implicit declaration of function 'static_branch'
> /next/linux-next-20120125/include/linux/jump_label.h:43:29: error: conflicting types for 'static_branch'
>
> Full randconfig file is attached.
Without having to add randomness, also in m68k/allmodconfig, now in Linus'
tree :-(
http://kisskb.ellerman.id.au/kisskb/buildresult/5491860/
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2012-01-26 17:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 3:19 linux-next: Tree for Jan 25 Stephen Rothwell
2012-01-25 19:07 ` linux-next: Tree for Jan 25 (net/sock.h, jump_label, memcg) Randy Dunlap
2012-01-26 17:18 ` Geert Uytterhoeven [this message]
2012-01-26 18:43 ` David Miller
2012-01-26 20:31 ` Glauber Costa
2012-01-26 21:46 ` Stephen Rothwell
2012-01-26 21:47 ` Glauber Costa
2012-01-25 21:52 ` [PATCH -next] uwb & wusb: fix kconfig error Randy Dunlap
2012-01-27 23:47 ` [PATCH -next] uwb & wusb & usb wireless controllers: fix kconfig error & build errors Randy Dunlap
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=CAMuHMdWp1wEHqPXNs+kaMYpomJnfbZPJjRk5GVFCuCL4Q5zK7g@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=gleb@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--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).