netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Preisner <thomas.preisner+linux@fau.de>
To: dave@thedillows.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kernel@i4.cs.fau.de, milan.stephan+linux@fau.de,
	thomas.preisner+linux@fau.de, sergei.shtylyov@cogentembedded.com,
	davem@davemloft.net
Subject: Re: Re: [PATCH v3 2/2] drivers: net: ethernet: 3com: fix return value
Date: Fri, 30 Dec 2016 03:37:52 +0100	[thread overview]
Message-ID: <1483065474-11512-1-git-send-email-thomas.preisner+linux@fau.de> (raw)
In-Reply-To: <1482873453.20986.4.camel@dillow-glaptop.roam.corp.google.com>

On Tue, 2016-12-27 at 22:17:35 +0100, David Dillow wrote:
>On Sun, 2016-12-25 at 01:30 +0100, Thomas Preisner wrote:
>> In some cases the return value of a failing function is not being used
>> and the function typhoon_init_one() returns another negative error
>> code instead.
>
>I'm not sure these changes are especially valuable, since we'll need to
>look at the dmesg log anyways to figure out what went wrong, but again I
>don't feel strongly.
>
>Fix up the subject issues and I'm happy to ack them.

As requested, here are the patchsets with the fixed subjects.
The subjects aswell as the subject prefixes are more precise now.
Hopefully that's ok.

Patch 1:
Makes the function typhoon_init_one() return a negative error code instead of 0.

Patch 2 [Optional]:
Makes the function typhoon_init_one() return the return value of the
corresponding failing function calls instead of a "fixed" negative error code.

With Regards,
Milan and Thomas

  reply	other threads:[~2016-12-30  2:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-23 23:00 [PATCH] drivers: net: ethernet: 3com: fix return value Thomas Preisner
2016-12-24  1:05 ` David Dillow
2016-12-24 12:02   ` Thomas Preisner
2016-12-24 12:02     ` [PATCH v2 1/2] " Thomas Preisner
2016-12-24 19:06       ` Sergei Shtylyov
2016-12-25  0:30         ` Thomas Preisner
2016-12-25  0:30           ` [PATCH v3 " Thomas Preisner
2016-12-25  0:56             ` David Miller
2016-12-25  0:30           ` [PATCH v3 2/2] " Thomas Preisner
2016-12-25 10:07             ` Sergei Shtylyov
2016-12-27 21:17             ` David Dillow
2016-12-30  2:37               ` Thomas Preisner [this message]
2016-12-30  2:37                 ` [PATCH v4 1/2] net: 3com: typhoon: typhoon_init_one: fix incorrect return values Thomas Preisner
2016-12-30 20:27                   ` David Miller
2016-12-30  2:37                 ` [PATCH v4 2/2] net: 3com: typhoon: typhoon_init_one: make return values more specific Thomas Preisner
2016-12-30 20:27                   ` David Miller
2016-12-27 21:15           ` Re: [PATCH v2 1/2] drivers: net: ethernet: 3com: fix return value David Dillow
2016-12-24 12:02     ` [PATCH v2 2/2] " Thomas Preisner

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=1483065474-11512-1-git-send-email-thomas.preisner+linux@fau.de \
    --to=thomas.preisner+linux@fau.de \
    --cc=dave@thedillows.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@i4.cs.fau.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=milan.stephan+linux@fau.de \
    --cc=netdev@vger.kernel.org \
    --cc=sergei.shtylyov@cogentembedded.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;
as well as URLs for NNTP newsgroup(s).