netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: kjlu@umn.edu
Cc: pakki001@umn.edu, jcliburn@gmail.com, chris.snook@gmail.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ethernet: atl1e: checking the status of atl1e_write_phy_reg
Date: Thu, 27 Dec 2018 16:23:40 -0800 (PST)	[thread overview]
Message-ID: <20181227.162340.939249640603797331.davem@davemloft.net> (raw)
In-Reply-To: <20181226042321.74123-1-kjlu@umn.edu>

From: Kangjie Lu <kjlu@umn.edu>
Date: Tue, 25 Dec 2018 22:23:19 -0600

> atl1e_write_phy_reg() could fail. The fix issues an error message when
> it fails.
> 
> Signed-off-by: Kangjie Lu <kjlu@umn.edu>

Applied, thanks.

      reply	other threads:[~2018-12-28  0:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-26  4:23 [PATCH] ethernet: atl1e: checking the status of atl1e_write_phy_reg Kangjie Lu
2018-12-28  0:23 ` David Miller [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=20181227.162340.939249640603797331.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=chris.snook@gmail.com \
    --cc=jcliburn@gmail.com \
    --cc=kjlu@umn.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pakki001@umn.edu \
    /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).