From: ebiederm@xmission.com (Eric W. Biederman)
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
garyhade@us.ibm.com, pbadari@us.ibm.com,
"y-goto\@jp.fujitsu.com" <y-goto@jp.fujitsu.com>,
gregkh@suse.de
Subject: Re: sysfs_create_link_nowarn still remains (Was Re: mmotm 2009-06-03-16-33 uploaded
Date: Wed, 03 Jun 2009 20:49:08 -0700 [thread overview]
Message-ID: <m11vq0acaz.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <20090604123813.96c2c5a9.kamezawa.hiroyu@jp.fujitsu.com> (KAMEZAWA Hiroyuki's message of "Thu\, 4 Jun 2009 12\:38\:13 +0900")
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> writes:
2> On Wed, 03 Jun 2009 16:33:52 -0700
> akpm@linux-foundation.org wrote:
>
>> The mm-of-the-moment snapshot 2009-06-03-16-33 has been uploaded to
>>
>> http://userweb.kernel.org/~akpm/mmotm/
>>
>> and will soon be available at
>>
>> git://git.zen-sources.org/zen/mmotm.git
>>
> It seems sysfs_create_link_nowarn() is removed in linux-next.patch but
> driver/base/node.c still includes it.
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=c04fc586c1a480ba198f03ae7b6cbd7b57380b91
>
> How should we fix it ? Folllowing is a quick hack for compile but ...
> should be clarified by memory hotplug guys.
Greg has already dropped the patches so the should not appear it the next linux-next.
I think your patch is what we want I haven't had a chance to wrap my head around
all of that yet.
Eric
> ==
>
> sysfs_create_link_nowarn() is obsolete.
>
> Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> ---
> Index: mmotm-2.6.30-Jun3/drivers/base/node.c
> ===================================================================
> --- mmotm-2.6.30-Jun3.orig/drivers/base/node.c
> +++ mmotm-2.6.30-Jun3/drivers/base/node.c
> @@ -279,7 +279,7 @@ int register_mem_sect_under_node(struct
> continue;
> if (page_nid != nid)
> continue;
> - return sysfs_create_link_nowarn(&node_devices[nid].sysdev.kobj,
> + return sysfs_create_link(&node_devices[nid].sysdev.kobj,
> &mem_blk->sysdev.kobj,
> kobject_name(&mem_blk->sysdev.kobj));
> }
next prev parent reply other threads:[~2009-06-04 3:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 23:33 mmotm 2009-06-03-16-33 uploaded akpm
2009-06-04 3:38 ` sysfs_create_link_nowarn still remains (Was " KAMEZAWA Hiroyuki
2009-06-04 3:40 ` Greg KH
2009-06-04 3:49 ` Eric W. Biederman [this message]
2009-06-04 15:15 ` Gary Hade
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=m11vq0acaz.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=garyhade@us.ibm.com \
--cc=gregkh@suse.de \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.com \
--cc=y-goto@jp.fujitsu.com \
/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