From: Ralf Baechle <ralf@linux-mips.org>
To: David Miller <davem@davemloft.net>
Cc: florian@openwrt.org, netdev@vger.kernel.org, blogic@openwrt.org,
linux-mips@linux-mips.org, mbizon@freebox.fr, jogo@openwrt.org,
cernekee@gmail.com
Subject: Re: [PATCH net-next] bcm63xx_enet: add support Broadcom BCM6345 Ethernet
Date: Thu, 13 Jun 2013 15:59:21 +0200 [thread overview]
Message-ID: <20130613135921.GA22906@linux-mips.org> (raw)
In-Reply-To: <20130613.025619.2170890039313059326.davem@davemloft.net>
On Thu, Jun 13, 2013 at 02:56:19AM -0700, David Miller wrote:
> From: Florian Fainelli <florian@openwrt.org>
> Date: Thu, 13 Jun 2013 10:49:18 +0100
>
> > We are in the slow process to switch to Device Tree to precisely
> > eliminate all of this (although not everyone agrees yet on the
> > details). Hopefully you should not see such things in the future.
>
> Fair enough, I'll put this patch back into my TODO queue.
David is right, one pair of welding goggles isn't enough to cope with the
uglyness of this but as a temporary thing I can live with it, so
Acked-by: Ralf Baechle <ralf@linux-mips.org>
Dave, feel free to merge this through next-next. I'm going to drop
this patch from the MIPS patchwork then.
Ralf
next prev parent reply other threads:[~2013-06-13 13:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 19:53 [PATCH net-next] bcm63xx_enet: add support Broadcom BCM6345 Ethernet Florian Fainelli
2013-06-13 8:44 ` David Miller
[not found] ` <CAGVrzcYE4VDWtL_Uj1DrkZ6GqX6ghqPAXPpyLptc6PGwReixSQ@mail.gmail.com>
2013-06-13 9:25 ` David Miller
2013-06-13 9:49 ` Florian Fainelli
2013-06-13 9:55 ` Florian Fainelli
2013-06-13 9:56 ` David Miller
2013-06-13 13:59 ` Ralf Baechle [this message]
2013-06-14 0:22 ` David Miller
2013-06-13 14:24 ` Maxime Bizon
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=20130613135921.GA22906@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=blogic@openwrt.org \
--cc=cernekee@gmail.com \
--cc=davem@davemloft.net \
--cc=florian@openwrt.org \
--cc=jogo@openwrt.org \
--cc=linux-mips@linux-mips.org \
--cc=mbizon@freebox.fr \
--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 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.