From: Alex Chiang <achiang@hp.com>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] mm: add numa node symlink for cpu devices in sysfs
Date: Wed, 21 Oct 2009 13:30:02 -0600 [thread overview]
Message-ID: <20091021193002.GI14102@ldl.fc.hp.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0910201407190.27248@chino.kir.corp.google.com>
* David Rientjes <rientjes@google.com>:
> On Tue, 20 Oct 2009, Alex Chiang wrote:
> > * David Rientjes <rientjes@google.com>:
> > > The return values of register_cpu_under_node() and
> > > unregister_cpu_under_node() are always ignored, so it would probably be
> > > best to convert these to be void functions. That doesn't mean you can
> > > simply ignore the result of the first sysfs_create_link(), though: the
> > > second should probably be suppressed if the first returns an error.
> >
> > I didn't want to change too much in the patch. Changing the
> > function signature seems a bit overeager, but if you have strong
> > feelings, I can do so.
>
> It's entirely up to you if you want to change them to be void. I thought
> it would be cleaner if the first patch in the series would convert them to
> void on the basis that the return value is never actually used and then
> the following patches simply return on error conditions.
I made the conversion as you suggested, but discovered under
sparse that:
drivers/base/node.c: In function ‘register_cpu_under_node’:
drivers/base/node.c:245: warning: ignoring return value of
‘sysfs_create_link’, declared with attribute warn_unused_result
I wasn't very happy with the result after doing something with
the return value of sysfs_create_link to make sparse shutup.
Seemed unnatural and very much had the feeling of jumping through
hoops just to make an automated tool be quiet.
So, I'll just leave [un]register_cpu_under_node() as returning
int. It not only makes the patch feel better, but if we do ever
want to decide to unroll due to an error in sysfs_create_link,
we'll have the information available at the callsites.
Thanks.
/ac
WARNING: multiple messages have this Message-ID (diff)
From: Alex Chiang <achiang@hp.com>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] mm: add numa node symlink for cpu devices in sysfs
Date: Wed, 21 Oct 2009 13:30:02 -0600 [thread overview]
Message-ID: <20091021193002.GI14102@ldl.fc.hp.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0910201407190.27248@chino.kir.corp.google.com>
* David Rientjes <rientjes@google.com>:
> On Tue, 20 Oct 2009, Alex Chiang wrote:
> > * David Rientjes <rientjes@google.com>:
> > > The return values of register_cpu_under_node() and
> > > unregister_cpu_under_node() are always ignored, so it would probably be
> > > best to convert these to be void functions. That doesn't mean you can
> > > simply ignore the result of the first sysfs_create_link(), though: the
> > > second should probably be suppressed if the first returns an error.
> >
> > I didn't want to change too much in the patch. Changing the
> > function signature seems a bit overeager, but if you have strong
> > feelings, I can do so.
>
> It's entirely up to you if you want to change them to be void. I thought
> it would be cleaner if the first patch in the series would convert them to
> void on the basis that the return value is never actually used and then
> the following patches simply return on error conditions.
I made the conversion as you suggested, but discovered under
sparse that:
drivers/base/node.c: In function a??register_cpu_under_nodea??:
drivers/base/node.c:245: warning: ignoring return value of
a??sysfs_create_linka??, declared with attribute warn_unused_result
I wasn't very happy with the result after doing something with
the return value of sysfs_create_link to make sparse shutup.
Seemed unnatural and very much had the feeling of jumping through
hoops just to make an automated tool be quiet.
So, I'll just leave [un]register_cpu_under_node() as returning
int. It not only makes the patch feel better, but if we do ever
want to decide to unroll due to an error in sysfs_create_link,
we'll have the information available at the callsites.
Thanks.
/ac
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-10-21 19:30 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-19 21:34 [PATCH 0/5] mm: modest useability enhancements for node sysfs attrs Alex Chiang
2009-10-19 21:34 ` Alex Chiang
2009-10-19 21:34 ` [PATCH 1/5] mm: add numa node symlink for memory section in sysfs Alex Chiang
2009-10-19 21:34 ` Alex Chiang
2009-10-20 11:55 ` KAMEZAWA Hiroyuki
2009-10-20 11:55 ` KAMEZAWA Hiroyuki
2009-10-21 18:27 ` Alex Chiang
2009-10-21 18:27 ` Alex Chiang
2009-10-19 21:34 ` [PATCH 2/5] mm: refactor register_cpu_under_node() Alex Chiang
2009-10-19 21:34 ` Alex Chiang
2009-10-19 21:34 ` [PATCH 3/5] mm: refactor unregister_cpu_under_node() Alex Chiang
2009-10-19 21:34 ` Alex Chiang
2009-10-19 21:34 ` [PATCH 4/5] mm: add numa node symlink for cpu devices in sysfs Alex Chiang
2009-10-19 21:34 ` Alex Chiang
2009-10-20 3:18 ` David Rientjes
2009-10-20 3:18 ` David Rientjes
2009-10-20 20:41 ` Alex Chiang
2009-10-20 20:41 ` Alex Chiang
2009-10-20 21:09 ` David Rientjes
2009-10-20 21:09 ` David Rientjes
2009-10-21 19:30 ` Alex Chiang [this message]
2009-10-21 19:30 ` Alex Chiang
2009-10-19 21:34 ` [PATCH 5/5] Documentation: ABI: document /sys/devices/system/cpu/ Alex Chiang
2009-10-19 21:34 ` Alex Chiang
2009-10-20 3:28 ` David Rientjes
2009-10-20 3:28 ` David Rientjes
2009-10-20 20:47 ` Alex Chiang
2009-10-20 20:47 ` Alex Chiang
2009-10-20 21:13 ` David Rientjes
2009-10-20 21:13 ` David Rientjes
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=20091021193002.GI14102@ldl.fc.hp.com \
--to=achiang@hp.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.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 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.