From: Ralf Baechle <ralf@linux-mips.org>
To: Maxime Bizon <mbizon@freebox.fr>
Cc: linux-mips@linux-mips.org, Florian Fainelli <florian@openwrt.org>
Subject: Re: More updates to bcm63xx
Date: Tue, 18 Aug 2009 15:37:07 +0100 [thread overview]
Message-ID: <20090818143707.GA2327@linux-mips.org> (raw)
In-Reply-To: <1250605887.23717.188.camel@sakura.staff.proxad.net>
On Tue, Aug 18, 2009 at 04:31:27PM +0200, Maxime Bizon wrote:
> > I folded all 8 patches into the existing patches for the linux-bcm63xx
> > tree
>
> The bcm63xx tree seems wrong.
>
> The patch from Florian that adds support for 6338 & 6345 is merged with
> commit BCM63XX: Add integrated ethernet mac support.
>
> The final patch that adds the board code is gone.
I'm just folding some of the patches together. I'm aware something went
wrong with the ethernet support and I'm sorting that out now.
Ralf
next prev parent reply other threads:[~2009-08-18 14:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 14:02 More updates to bcm63xx Maxime Bizon
2009-06-03 14:02 ` [PATCH 1/8] bcm63xx: register gpiochip in prom Maxime Bizon
2009-06-03 14:02 ` [PATCH 2/8] bcm63xx: register correct number of gpio for 6358 Maxime Bizon
2009-06-03 14:02 ` [PATCH 3/8] bcm63xx: fix gpio set Maxime Bizon
2009-06-03 14:02 ` [PATCH 4/8] bcm63xx: restore spinlock in gpio Maxime Bizon
2009-06-03 14:02 ` [PATCH 5/8] bcm63xx: request gpio before using it in bcm63xx_pcmcia Maxime Bizon
2009-06-03 14:02 ` [PATCH 6/8] bcm63xx: add missing null entry in bcm63xx_pcmcia pci device table Maxime Bizon
2009-06-03 14:02 ` [PATCH 7/8] bcm63xx: fix bcm63xx_pcmcia device removal Maxime Bizon
2009-06-03 14:02 ` [PATCH 8/8] bcm63xx: fix oops when removing bcm63xx_enet module Maxime Bizon
2009-08-18 12:24 ` More updates to bcm63xx Ralf Baechle
2009-08-18 14:31 ` Maxime Bizon
2009-08-18 14:37 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-02 23:47 Maxime Bizon
2009-06-03 6:06 ` 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=20090818143707.GA2327@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;
as well as URLs for NNTP newsgroup(s).