From: Francois Romieu <romieu@fr.zoreil.com>
To: Hayes Wang <hayeswang@realtek.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 5/5] r8169: support RTL8411
Date: Thu, 29 Mar 2012 11:12:29 +0200 [thread overview]
Message-ID: <20120329091229.GA22410@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <1332923214-5071-5-git-send-email-hayeswang@realtek.com>
Hayes Wang <hayeswang@realtek.com> :
> Support the new chip RTL8411.
>
> Signed-off-by: Hayes Wang <hayeswang@realtek.com>
> ---
> drivers/net/ethernet/realtek/r8169.c | 142 +++++++++++++++++++++++++++++++++-
> 1 files changed, 139 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/ethernet/realtek/r8169.c b/drivers/net/ethernet/realtek/r8169.c
> index cde5cea..d00f4e9 100644
> --- a/drivers/net/ethernet/realtek/r8169.c
> +++ b/drivers/net/ethernet/realtek/r8169.c
[...]
> @@ -250,7 +252,10 @@ static const struct {
> JUMBO_9K, false),
> [RTL_GIGA_MAC_VER_37] =
> _R("RTL8402", RTL_TD_1, FIRMWARE_8402_1,
> - JUMBO_1K, true)
> + JUMBO_1K, true),
> + [RTL_GIGA_MAC_VER_38] =
> + _R("RTL8411", RTL_TD_1, FIRMWARE_8411_1,
> + JUMBO_9K, false)
rtl_init_jumbo_ops probably needs to be updated as well.
Nit: please keep a colon in 'JUMBO_9K, false),'.
^
There was one after the (not so) last record before patch 03/05 and I would
prefer it to stay because new devices are regularly added. The '-' line is
only noise.
Thanks.
--
Ueimor
prev parent reply other threads:[~2012-03-29 9:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 8:26 [PATCH net-next v2 1/5] r8169: modify pll power function Hayes Wang
2012-03-28 8:26 ` [PATCH net-next v2 2/5] r8169: add csi_opt Hayes Wang
2012-03-28 8:26 ` [PATCH net-next v2 3/5] r8169: support RTL8402 Hayes Wang
2012-03-28 8:26 ` [PATCH net-next v2 4/5] r8169: adjust some functions of 8111f Hayes Wang
2012-03-28 8:26 ` [PATCH net-next v2 5/5] r8169: support RTL8411 Hayes Wang
2012-03-29 9:12 ` Francois Romieu [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=20120329091229.GA22410@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=hayeswang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®