All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/4] net: Update README.drivers.eth to mention latest APIs
Date: Wed, 25 Mar 2015 16:34:54 -0600	[thread overview]
Message-ID: <CAPnjgZ2mW8Hr07tg6hbKjwRozxcL2XaYDZwdXSFnwLjcUGyLqQ@mail.gmail.com> (raw)
In-Reply-To: <CANr=Z=Ydq2MZS79qYntDCLPir8ucSpbwCwFu+g5a8ab0L2oDVA@mail.gmail.com>

On 20 March 2015 at 13:18, Joe Hershberger <joe.hershberger@gmail.com> wrote:
> On Fri, Mar 20, 2015 at 4:12 AM, Bin Meng <bmeng.cn@gmail.com> wrote:
>>
>> README.drivers.eth still refers to the deprecated miiphy_register().
>> Update the doc to mention new APIs mdio_alloc() and mdio_register().
>>
>> Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
>> ---
>
> Acked-by: Joe Hershberger <joe.hershberger@ni.com>

Applied to u-boot-x86, thanks!

  reply	other threads:[~2015-03-25 22:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-20  9:12 [U-Boot] [PATCH 0/4] x86: Add Intel Topcliff PCH Gigabit Ethernet support Bin Meng
2015-03-20  9:12 ` [U-Boot] [PATCH 1/4] net: Add ethernet FCS length macro in net.h Bin Meng
2015-03-20 19:18   ` Joe Hershberger
2015-03-25 22:34     ` Simon Glass
2015-03-20  9:12 ` [U-Boot] [PATCH 2/4] net: Update README.drivers.eth to mention latest APIs Bin Meng
2015-03-20 19:18   ` Joe Hershberger
2015-03-25 22:34     ` Simon Glass [this message]
2015-03-20  9:12 ` [U-Boot] [PATCH 3/4] net: Add Intel Topcliff GMAC driver Bin Meng
2015-03-20 19:18   ` Joe Hershberger
2015-03-23 21:57     ` Simon Glass
2015-03-24  1:24       ` Bin Meng
2015-03-24  4:18         ` Simon Glass
2015-03-24  4:54           ` Bin Meng
2015-03-25 22:34             ` Simon Glass
2015-03-20  9:12 ` [U-Boot] [PATCH 4/4] x86: crownbay: Enable Intel Topcliff GMAC support Bin Meng
2015-03-20 19:18   ` Joe Hershberger
2015-03-25 22:35     ` Simon Glass
2015-03-20 19:18 ` [U-Boot] [PATCH 0/4] x86: Add Intel Topcliff PCH Gigabit Ethernet support Joe Hershberger
2015-03-20 19:58   ` Simon Glass

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=CAPnjgZ2mW8Hr07tg6hbKjwRozxcL2XaYDZwdXSFnwLjcUGyLqQ@mail.gmail.com \
    --to=sjg@chromium.org \
    --cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.