netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: oneukum@suse.de
Cc: netdev@vger.kernel.org, nic_swsd@realtek.com
Subject: Re: [PATCH] r8152: correct error returns
Date: Sat, 02 Aug 2014 16:34:18 -0700 (PDT)	[thread overview]
Message-ID: <20140802.163418.1314777407262254543.davem@davemloft.net> (raw)
In-Reply-To: <1406901370-6847-1-git-send-email-oneukum@suse.de>

From: Oliver Neukum <oneukum@suse.de>
Date: Fri,  1 Aug 2014 15:56:10 +0200

> If an autoresume fails the internal error codes of the PM
> subsystem mustn't be leaked to user space. Replace them by EIO
> 
> Signed-off-by: Oliver Neukum <oneukum@suse.de>

Really?

Then even the core usbnet driver gets this wrong, as well as many
other drivers I scanned over for this problem.

  reply	other threads:[~2014-08-02 23:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-01 13:56 [PATCH] r8152: correct error returns Oliver Neukum
2014-08-02 23:34 ` David Miller [this message]
2014-08-03  7:06   ` Oliver Neukum
2014-08-04 22:18     ` David Miller
2014-08-05  7:43       ` Oliver Neukum
2014-08-05 19:52         ` David Miller

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=20140802.163418.1314777407262254543.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=nic_swsd@realtek.com \
    --cc=oneukum@suse.de \
    /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).