From: Ralf Baechle <ralf@linux-mips.org>
To: Florian Fainelli <florian@openwrt.org>
Cc: linux-mips@linux-mips.org, Maxime Bizon <mbizon@freebox.fr>
Subject: Re: [PATCH 10/10] bcm63xx: compile fixes for bcm63xx_enet.c
Date: Mon, 1 Jun 2009 15:55:52 +0100 [thread overview]
Message-ID: <20090601145552.GI6604@linux-mips.org> (raw)
In-Reply-To: <200905312031.35241.florian@openwrt.org>
On Sun, May 31, 2009 at 08:31:34PM +0200, Florian Fainelli wrote:
> This patch makes the ethernet driver compile again
> after commit 908a7a1. netif_rx_schedule became
> napi_schedule and __netif_rx_complete became
> __napi_rx_complete.
>
> Signed-off-by: Florian Fainelli <florian@openwrt.org>
Folded into the "MIPS: BCM63XX: Add integrated ethernet mac support."
patch.
You should eventually run this patch by the network maintainers. It's
a driver patch so I won't merge it upstream unless it's been acked by one
of the network guys.
Thanks,
Ralf
next prev parent reply other threads:[~2009-06-01 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-31 18:31 [PATCH 10/10] bcm63xx: compile fixes for bcm63xx_enet.c Florian Fainelli
2009-06-01 14:55 ` Ralf Baechle [this message]
2009-06-01 15:02 ` Florian Fainelli
2009-06-02 9:25 ` Ralf Baechle
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=20090601145552.GI6604@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=florian@openwrt.org \
--cc=linux-mips@linux-mips.org \
--cc=mbizon@freebox.fr \
/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