From: Tom Rini <trini@konsulko.com>
To: Sergei Antonov <saproj@gmail.com>
Cc: u-boot@lists.denx.de, rfried.dev@gmail.com, joe.hershberger@ni.com
Subject: Re: [PATCH v3 1/3] net: ftmac100: change driver name from nds32_mac to ftmac100
Date: Fri, 10 Feb 2023 13:44:42 -0500 [thread overview]
Message-ID: <Y+aQmrrX5Gh0yBlf@bill-the-cat> (raw)
In-Reply-To: <20230203190904.2448780-1-saproj@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 403 bytes --]
On Fri, Feb 03, 2023 at 10:09:02PM +0300, Sergei Antonov wrote:
> So it will be named similarly to the related ftgmac100 driver.
> The old name 'nds32_mac' is not referred to anywhere in U-Boot.
>
> Signed-off-by: Sergei Antonov <saproj@gmail.com>
> Reviewed-by: Ramon Fried <rfried.dev@gmail.com>
> Reviewed-by: Rick Chen <rick@andestech.com>
Applied to u-boot/master, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2023-02-10 18:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 19:09 [PATCH v3 1/3] net: ftmac100: change driver name from nds32_mac to ftmac100 Sergei Antonov
2023-02-03 19:09 ` [PATCH v3 2/3] net: ftmac100: simplify priv->iobase casting Sergei Antonov
[not found] ` <PU1PR03MB29978B9E3B4A4AF70E5FB191C1D99@PU1PR03MB2997.apcprd03.prod.outlook.com>
2023-02-09 2:46 ` Rick Chen
2023-02-10 18:44 ` Tom Rini
2023-02-03 19:09 ` [PATCH v3 3/3] net: ftmac100: add mii read and write callbacks Sergei Antonov
[not found] ` <PU1PR03MB2997F582BB6AC65F0FF4ABCAC1D99@PU1PR03MB2997.apcprd03.prod.outlook.com>
2023-02-09 3:09 ` Rick Chen
2023-02-10 18:44 ` Tom Rini
[not found] ` <PU1PR03MB2997239CB9B1B68FEC3D2929C1D99@PU1PR03MB2997.apcprd03.prod.outlook.com>
2023-02-09 2:00 ` [PATCH v3 1/3] net: ftmac100: change driver name from nds32_mac to ftmac100 Rick Chen
2023-02-10 18:44 ` Tom Rini [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=Y+aQmrrX5Gh0yBlf@bill-the-cat \
--to=trini@konsulko.com \
--cc=joe.hershberger@ni.com \
--cc=rfried.dev@gmail.com \
--cc=saproj@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox