From: Glauber Costa <glommer@parallels.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: linux-next: Tree for Jan 19 (mm/memcontrol.c)
Date: Fri, 20 Jan 2012 15:09:17 +0400 [thread overview]
Message-ID: <4F194B5D.6080701@parallels.com> (raw)
In-Reply-To: <20120120090037.e32a119f.kamezawa.hiroyu@jp.fujitsu.com>
On 01/20/2012 04:00 AM, KAMEZAWA Hiroyuki wrote:
> On Thu, 19 Jan 2012 14:35:03 -0800
> Randy Dunlap<rdunlap@xenotime.net> wrote:
>
>> On 01/18/2012 05:59 PM, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20120118:
>>
>>
>> on i386:
>>
>> mm/built-in.o:(__jump_table+0x8): undefined reference to `memcg_socket_limit_enabled'
>> mm/built-in.o:(__jump_table+0x14): undefined reference to `memcg_socket_limit_enabled'
>>
>>
>> Full randconfig file is attached.
>>
>
> Thank you. Forwarding this to Costa.
>
> Thanks,
> -Kame
>
Oh dear lord... So what happened here, is that I moved this code out of
CONFIG_INET to fix another problem, and forgot that it needed to be
wrapped under CONFIG_NET instead.
It is not an excuse, but I did compiled it over at least 6 random
configs, and thought it was okay. I guess so many things select
CONFIG_NET that it ends up being hard to generate a config without it.
I think the fix for this needs to go through dave's tree, since it is
where the original fix went through.
I will send a fix shortly.
WARNING: multiple messages have this Message-ID (diff)
From: Glauber Costa <glommer@parallels.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: linux-next: Tree for Jan 19 (mm/memcontrol.c)
Date: Fri, 20 Jan 2012 15:09:17 +0400 [thread overview]
Message-ID: <4F194B5D.6080701@parallels.com> (raw)
In-Reply-To: <20120120090037.e32a119f.kamezawa.hiroyu@jp.fujitsu.com>
On 01/20/2012 04:00 AM, KAMEZAWA Hiroyuki wrote:
> On Thu, 19 Jan 2012 14:35:03 -0800
> Randy Dunlap<rdunlap@xenotime.net> wrote:
>
>> On 01/18/2012 05:59 PM, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20120118:
>>
>>
>> on i386:
>>
>> mm/built-in.o:(__jump_table+0x8): undefined reference to `memcg_socket_limit_enabled'
>> mm/built-in.o:(__jump_table+0x14): undefined reference to `memcg_socket_limit_enabled'
>>
>>
>> Full randconfig file is attached.
>>
>
> Thank you. Forwarding this to Costa.
>
> Thanks,
> -Kame
>
Oh dear lord... So what happened here, is that I moved this code out of
CONFIG_INET to fix another problem, and forgot that it needed to be
wrapped under CONFIG_NET instead.
It is not an excuse, but I did compiled it over at least 6 random
configs, and thought it was okay. I guess so many things select
CONFIG_NET that it ends up being hard to generate a config without it.
I think the fix for this needs to go through dave's tree, since it is
where the original fix went through.
I will send a fix shortly.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Glauber Costa <glommer@parallels.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
Stephen Rothwell <sfr@canb.auug.org.au>,
<linux-next@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: linux-next: Tree for Jan 19 (mm/memcontrol.c)
Date: Fri, 20 Jan 2012 15:09:17 +0400 [thread overview]
Message-ID: <4F194B5D.6080701@parallels.com> (raw)
In-Reply-To: <20120120090037.e32a119f.kamezawa.hiroyu@jp.fujitsu.com>
On 01/20/2012 04:00 AM, KAMEZAWA Hiroyuki wrote:
> On Thu, 19 Jan 2012 14:35:03 -0800
> Randy Dunlap<rdunlap@xenotime.net> wrote:
>
>> On 01/18/2012 05:59 PM, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20120118:
>>
>>
>> on i386:
>>
>> mm/built-in.o:(__jump_table+0x8): undefined reference to `memcg_socket_limit_enabled'
>> mm/built-in.o:(__jump_table+0x14): undefined reference to `memcg_socket_limit_enabled'
>>
>>
>> Full randconfig file is attached.
>>
>
> Thank you. Forwarding this to Costa.
>
> Thanks,
> -Kame
>
Oh dear lord... So what happened here, is that I moved this code out of
CONFIG_INET to fix another problem, and forgot that it needed to be
wrapped under CONFIG_NET instead.
It is not an excuse, but I did compiled it over at least 6 random
configs, and thought it was okay. I guess so many things select
CONFIG_NET that it ends up being hard to generate a config without it.
I think the fix for this needs to go through dave's tree, since it is
where the original fix went through.
I will send a fix shortly.
next prev parent reply other threads:[~2012-01-20 11:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 1:59 linux-next: Tree for Jan 19 Stephen Rothwell
2012-01-19 3:07 ` linux-next: Tree for Jan 19 (uml) Randy Dunlap
2012-01-19 2:18 ` Stephen Rothwell
2012-01-19 3:40 ` Linus Torvalds
2012-01-19 22:27 ` linux-next: Tree for Jan 19 (block/nvme) Randy Dunlap
2012-01-19 22:35 ` linux-next: Tree for Jan 19 (mm/memcontrol.c) Randy Dunlap
2012-01-20 0:00 ` KAMEZAWA Hiroyuki
2012-01-20 0:00 ` KAMEZAWA Hiroyuki
2012-01-20 11:09 ` Glauber Costa [this message]
2012-01-20 11:09 ` Glauber Costa
2012-01-20 11:09 ` Glauber Costa
2012-01-19 23:43 ` linux-next: Tree for Jan 19 (cisco/enic) Randy Dunlap
2012-01-20 5:33 ` Roopa Prabhu
2012-01-20 5:33 ` Roopa Prabhu
2012-01-20 5:45 ` Roopa Prabhu
2012-01-20 5:45 ` Roopa Prabhu
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=4F194B5D.6080701@parallels.com \
--to=glommer@parallels.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@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.