From: Florian Fainelli <f.fainelli@gmail.com>
To: Kangjie Lu <kjlu@umn.edu>
Cc: pakki001@umn.edu, Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dsa: return error code upstream
Date: Wed, 26 Dec 2018 09:31:01 -0800 [thread overview]
Message-ID: <b01ffe9c-590c-ef93-e9c0-6a2a3321979d@gmail.com> (raw)
In-Reply-To: <20181226040818.73764-1-kjlu@umn.edu>
Le 12/25/18 à 8:08 PM, Kangjie Lu a écrit :
> Both bcm_sf2_sw_indir_rw and mdiobus_write_nested could fail, so let's
> return their error codes upstream.
Thanks for your patch, the subject should be:
net: dsa: bcm_sf2: Propagate error value from mdio_write
to match existing commits done to that file. Thanks!
--
Florian
next prev parent reply other threads:[~2018-12-26 17:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-26 4:08 [PATCH] dsa: return error code upstream Kangjie Lu
2018-12-26 17:31 ` Florian Fainelli [this message]
2018-12-28 0:22 ` David Miller
2018-12-28 1:06 ` Florian Fainelli
2018-12-28 1:53 ` 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=b01ffe9c-590c-ef93-e9c0-6a2a3321979d@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=kjlu@umn.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pakki001@umn.edu \
--cc=vivien.didelot@gmail.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