public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: "Zhang, Rui" <rui.zhang@intel.com>,
	linux-acpi@vger.kernel.org, linux-pm@lists.linux-foundation.org
Subject: Re: [patch 2.6.25-rc2-git] crosslink ACPI and "real" device nodes
Date: Tue, 26 Feb 2008 18:19:31 -0800	[thread overview]
Message-ID: <200802261819.31755.david-b@pacbell.net> (raw)
In-Reply-To: <20080226131058.GA8234@khazad-dum.debian.net>

On Tuesday 26 February 2008, Henrique de Moraes Holschuh wrote:
> On Mon, 25 Feb 2008, David Brownell wrote:
> > int __must_check sysfs_create_link(struct kobject *kobj, struct kobject *target,
> >                                    const char *name);
> > 
> > Perhaps you disabled those warnings.  (And FWIW, I don't see any
> > reasonable way to handle such faults, so ignoring them is thus
> > the right "solution".)
> 
> You issue a printk warning the user, and try to continue.

That's not "handling" in any useful sense though.  There's no
question about "try" to continue, by the way ... from inside
the kernel this information is completely non-essential.

- Dave



  reply	other threads:[~2008-02-27  2:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-23  5:54 [patch 2.6.25-rc2-git] crosslink ACPI and "real" device nodes David Brownell
2008-02-25 21:47 ` Zhang, Rui
2008-02-26  6:45   ` David Brownell
2008-02-25 22:10     ` Zhang, Rui
2008-02-26  7:17       ` David Brownell
2008-02-26 13:10         ` Henrique de Moraes Holschuh
2008-02-27  2:19           ` David Brownell [this message]
2008-03-08 19:47             ` David Brownell

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=200802261819.31755.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=hmh@hmh.eng.br \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=rui.zhang@intel.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