From: David Miller <davem@davemloft.net>
To: rdunlap@xenotime.net
Cc: sfr@canb.auug.org.au, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
glommer@parallels.com
Subject: Re: linux-next: Tree for Jan 13 (net core)
Date: Fri, 13 Jan 2012 13:55:45 -0800 (PST) [thread overview]
Message-ID: <20120113.135545.2287769681500341872.davem@davemloft.net> (raw)
In-Reply-To: <4F10AFD3.7050505@xenotime.net>
From: Randy Dunlap <rdunlap@xenotime.net>
Date: Fri, 13 Jan 2012 14:27:31 -0800
> On 01/12/2012 08:58 PM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20120112:
>
>
> net/built-in.o: In function `sk_clone_lock':
> (.text+0x45ed): undefined reference to `sock_update_memcg'
>
> Full randconfig file is attached.
Grrr, Glauber another regression...
next prev parent reply other threads:[~2012-01-13 21:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 4:58 linux-next: Tree for Jan 13 Stephen Rothwell
2012-01-13 22:27 ` linux-next: Tree for Jan 13 (net core) Randy Dunlap
2012-01-13 21:55 ` David Miller [this message]
2012-01-13 22:40 ` linux-next: Tree for Jan 13 (lib/digsig.c) Randy Dunlap
2012-01-17 9:48 ` Kasatkin, Dmitry
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=20120113.135545.2287769681500341872.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=glommer@parallels.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.