From: David Miller <davem@davemloft.net>
To: linux@roeck-us.net
Cc: adi-buildroot-devel@lists.sourceforge.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
andrew@lunn.ch
Subject: Re: [PATCH -next] net: bfin_mac: Use phy_find_first() instead of open-coding it
Date: Mon, 11 Jan 2016 00:00:59 -0500 (EST) [thread overview]
Message-ID: <20160111.000059.2259197091861211706.davem@davemloft.net> (raw)
In-Reply-To: <1452487429-6197-1-git-send-email-linux@roeck-us.net>
From: Guenter Roeck <linux@roeck-us.net>
Date: Sun, 10 Jan 2016 20:43:49 -0800
> Use phy_find_first() to find the first phy device instead of
> open-coding it.
>
> Cc: Andrew Lunn <andrew@lunn.ch>
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Applied.
prev parent reply other threads:[~2016-01-11 5:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 4:43 [PATCH -next] net: bfin_mac: Use phy_find_first() instead of open-coding it Guenter Roeck
2016-01-11 5:00 ` 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=20160111.000059.2259197091861211706.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=adi-buildroot-devel@lists.sourceforge.net \
--cc=andrew@lunn.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).