All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Eisele <konrad@gaisler.com>
To: sparclinux@vger.kernel.org
Subject: Re: Leon patches...
Date: Mon, 02 Nov 2009 13:13:35 +0000	[thread overview]
Message-ID: <4AEEDAFF.8040902@gaisler.com> (raw)
In-Reply-To: <20091102.042421.72817389.davem@davemloft.net>

David Miller wrote:
> Konrad, I've just done a review of the two pending Leon patches.
> Sorry for taking so long.
> 
> The SMP patch looks fine, I've applied it to sparc-next-2.6 and am
> doing some build validation tests before pushing it out to kernel.org
> 

O, that is great news.

> The AMBA device patch needs a little bit of work.
> 
> I think you should create a CONFIG_AMBA in drivera/ambapp/Kconfig
> that protects everything.  CONFIG_AMBA should "depends on SPARC_LEON"
> 
> Then drivers/Makefile should only traverse down into ambapp/
> if CONFIG_AMBA is set, just as we do for other bus layers such
> as PCI.
> 
> Fix that up and I'll try to add the Amba patch into sparc-next-2.6
> too, thanks!

I'll do that in the new version of the patch.
We are currently trying to rewrite this patch anyway:
kristoffer@gaisler.com sent the uart driver (that was included
in the AMBA device patch) to linux-serial instead. He seem to have
rewritten it so that it was only dependent on Openfirmware, not the
AMBA plug and play scanning. So, I'll have to rewrite this patch anyway
and take that driver out. What remains will be the AMBA p&p scanning.

It'll take a  while to get a new patch.
Can you until then postphone the AMBA device patch so that
it (the new patch to be sent) might be applied at a later time?

-- Greetings Konrad


> 
> Thanks.
> 
> 


  parent reply	other threads:[~2009-11-02 13:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-02 12:24 Leon patches David Miller
2009-11-02 13:08 ` David Miller
2009-11-02 13:13 ` Konrad Eisele [this message]
2009-11-02 13:19 ` Kristoffer Glembo
2009-11-02 13:35 ` David Miller

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=4AEEDAFF.8040902@gaisler.com \
    --to=konrad@gaisler.com \
    --cc=sparclinux@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.