The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Akinobu Mita" <akinobu.mita@gmail.com>
To: "Linux Kernel List" <linux-kernel@vger.kernel.org>,
	"Greg KH" <greg@kroah.com>
Subject: Re: __must_check and driver model
Date: Tue, 27 Feb 2007 22:55:42 +0900	[thread overview]
Message-ID: <961aa3350702270555jecce07bge5e6a5f460ca7d12@mail.gmail.com> (raw)
In-Reply-To: <20070227120450.GB2154@flint.arm.linux.org.uk>

2007/2/27, Russell King <rmk+lkml@arm.linux.org.uk>:
> I'm still seeing lots of warnings about unchecked return codes from
> driver model functions.
>
> These must have been around for at least three months, if not longer,
> and there seems to be very little progress towards resolving them.
> Maybe if no one cares about fixing the warnings, we shouldn't have
> the warnings at all since they're just mere noise.

I have patch series to shut up __must_check warning about
sysfs_create_link() in drivers/base/core.c (I made before, but
I forgot to send)

      reply	other threads:[~2007-02-27 13:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-27 12:04 __must_check and driver model Russell King
2007-02-27 13:55 ` Akinobu Mita [this message]

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=961aa3350702270555jecce07bge5e6a5f460ca7d12@mail.gmail.com \
    --to=akinobu.mita@gmail.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    /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