From: linas@austin.ibm.com (Linas Vepstas)
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: ppc-dev <linuxppc-dev@ozlabs.org>,
Paul Mackerras <paulus@samba.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH] [POWERPC] remove build warnings in windfarm_core
Date: Tue, 15 May 2007 11:45:29 -0500 [thread overview]
Message-ID: <20070515164529.GA4383@austin.ibm.com> (raw)
In-Reply-To: <e1629d824068540e703ba7d661753992@kernel.crashing.org>
On Tue, May 15, 2007 at 08:32:08AM +0200, Segher Boessenkool wrote:
> >> - device_create_file(&wf_platform_device.dev, &new_ct->attr);
> >> + ret = device_create_file(&wf_platform_device.dev, &new_ct->attr);
> >> + if (ret) {
> >> + list_del(&new_ct->link);
> >> + printk(KERN_WARNING "windfarm: device_creat_file failed"
> >> + "for %s\n", new_ct->name);
> >> + goto out_unlock;
> >
> > This shows up why I hate the must_check stuff. The sysfs files are
> > not essential for the operation of the windfarm subsystem.
>
> They are essential for the user expectations of the
> subsystem though; if registration fails, a warning
> should be printed.
>
> > If the
> > sysfs registration fails for any reason, we now have a completely
> > non-functional windfarm subsystem instead of a mostly-working one. :(
>
> Yeah, but that's not must_check's fault, it doesn't
> say *what* to do with the error code :-)
Ergo, the patch should be reworked to print the warning only,
but otherwise continue with the setup.
--linas
next prev parent reply other threads:[~2007-05-15 16:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 6:32 [PATCH] [POWERPC] remove build warnings in windfarm_core Stephen Rothwell
2007-05-15 6:19 ` Paul Mackerras
2007-05-15 6:32 ` Segher Boessenkool
2007-05-15 16:45 ` Linas Vepstas [this message]
2007-05-16 1:24 ` Stephen Rothwell
2007-05-16 13:20 ` Segher Boessenkool
2007-05-16 14:10 ` Will Schmidt
2007-05-17 1:22 ` Stephen Rothwell
2007-05-17 1:26 ` Benjamin Herrenschmidt
2007-05-18 11:20 ` Geert Uytterhoeven
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=20070515164529.GA4383@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=segher@kernel.crashing.org \
--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).