From: Hauke Mehrtens <hauke@hauke-m.de>
To: "Rafał Miłecki" <zajec5@gmail.com>,
linux-mips@linux-mips.org, "Ralf Baechle" <ralf@linux-mips.org>
Subject: Re: [PATCH][RFC][Ack req] MIPS: BCM47XX: Initialize bcma bus later (with mm available)
Date: Wed, 03 Sep 2014 22:00:41 +0200 [thread overview]
Message-ID: <54077369.60102@hauke-m.de> (raw)
In-Reply-To: <1409658719-32110-1-git-send-email-zajec5@gmail.com>
On 09/02/2014 01:51 PM, Rafał Miłecki wrote:
> Initializaion with memory allocator available will be much simpler, this
> will allow cleanup in the bcma code.
>
> Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
Acked-by: Hauke Mehrtens <hauke@hauke-m.de>
> ---
> Hi Ralf,
>
> As recently described in the e-mail thread
> "Booting bcm47xx (bcma & stuff), sharing code with bcm53xx"
> I plan to simplify bcma code for SoC booting.
>
> This is one of my patches. As most of them touch "bcma" driver code, I
> wanted to push them through John's wireless-next tree. Of course this
> patch is not wireless related at all, so I'd need your Ack for it.
>
> Could you review it and let me know if it looks OK for you? Is that
> acceptable for you to push this one patch using wireless-next git tree?
>
> This patch already depends on two that were submitted to John:
> [PATCH 1/2] bcma: move bus struct setup into early part of host specific code
> [PATCH 2/2] bcma: use separated function to initialize bus on SoC
>
> Hauke: could you review it as well, please?
> ---
> arch/mips/bcm47xx/bcm47xx_private.h | 3 +++
> arch/mips/bcm47xx/irq.c | 8 ++++++++
> arch/mips/bcm47xx/setup.c | 33 +++++++++++++++++++++++++++------
> 3 files changed, 38 insertions(+), 6 deletions(-)
>
prev parent reply other threads:[~2014-09-03 20:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 11:51 [PATCH][RFC][Ack req] MIPS: BCM47XX: Initialize bcma bus later (with mm available) Rafał Miłecki
2014-09-03 20:00 ` Hauke Mehrtens [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=54077369.60102@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=zajec5@gmail.com \
/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