public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Haavard Skinnemoen <hskinnemoen@atmel.com>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: AVR32 architecture patch against Linux 2.6.18-rc1 available
Date: Thu, 6 Jul 2006 02:19:06 -0700	[thread overview]
Message-ID: <20060706021906.1af7ffa3.akpm@osdl.org> (raw)
In-Reply-To: <20060706105227.220565f8@cad-250-152.norway.atmel.com>

On Thu, 6 Jul 2006 10:52:27 +0200
Haavard Skinnemoen <hskinnemoen@atmel.com> wrote:

> Hi everyone,
> 
> I've put up an updated set of patches for AVR32 support at
> http://avr32linux.org/twiki/bin/view/Main/LinuxPatches
> 
> The most interesting patch probably is
> http://avr32linux.org/twiki/pub/Main/LinuxPatches/avr32-arch-2.patch
> 
> which, at 544K, is too large to attach here. Please let me know if you
> want me to do it anyway.
> 
> Anyone want to have a look at this? I understand that a full review is
> a huge job, but I'd appreciate a pointer or two in the general
> direction that I need to take this in order to get it acceptable for
> mainline.
> 

Looks pretty sane from a quick scan.

- request_irq() can use GFP_KERNEL?

- show_interrupts() should use for_each_online_cpu()

<wow, kprobes support>

- do you really need __udivdi3() and friends?  We struggle hard to avoid
  the necessity on x86 and you should be able to leverage that advantage.

- What are these for?

	+EXPORT_SYMBOL(register_dma_controller);
	+EXPORT_SYMBOL(find_dma_controller);

	+EXPORT_SYMBOL(clk_get);
	+EXPORT_SYMBOL(clk_put);
	+EXPORT_SYMBOL(clk_enable);
	+EXPORT_SYMBOL(clk_disable);
	+EXPORT_SYMBOL(clk_get_rate);
	+EXPORT_SYMBOL(clk_round_rate);
	+EXPORT_SYMBOL(clk_set_rate);
	+EXPORT_SYMBOL(clk_set_parent);
	+EXPORT_SYMBOL(clk_get_parent);

- Was there a ./MAINTAINERS patch?  I didn't see one.

- Who stands behind this port?  How do we know this isn't a patch-n-run
  exercise?  How do we know that the code won't rot?

- How does one build a something->avr32 cross-toolchain?

Thanks.

  reply	other threads:[~2006-07-06  9:19 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-06  8:52 AVR32 architecture patch against Linux 2.6.18-rc1 available Haavard Skinnemoen
2006-07-06  9:19 ` Andrew Morton [this message]
2006-07-06  9:51   ` Russell King
2006-07-06  9:58   ` Arjan van de Ven
2006-07-06 10:43     ` Haavard Skinnemoen
2006-07-06 15:17       ` Russell King
2006-07-06 10:03   ` Haavard Skinnemoen
2006-07-06 10:14     ` Andrew Morton
2006-07-06 13:57       ` Haavard Skinnemoen
2006-07-10  9:03       ` Haavard Skinnemoen
2006-07-10  9:31         ` Andrew Morton
2006-07-10  9:37         ` Andrew Morton
2006-07-10 11:04           ` Haavard Skinnemoen
2006-07-10  9:57         ` David Woodhouse
2006-07-10 11:25           ` Haavard Skinnemoen
2006-07-06 11:30     ` Thomas Gleixner
2006-07-06 11:50       ` Haavard Skinnemoen
2006-07-06 12:10         ` Thomas Gleixner
2006-07-06 11:58 ` David Woodhouse
2006-07-06 14:13   ` Haavard Skinnemoen
2006-07-06 14:34     ` David Woodhouse
2006-07-06 18:48       ` Haavard Skinnemoen
2006-07-06 23:17         ` David Woodhouse
2006-07-07 10:39   ` Haavard Skinnemoen
2006-07-07 10:44     ` Arjan van de Ven
2006-07-07  8:08 ` Nick Piggin
2006-07-07  8:18   ` Nick Piggin
2006-07-07 16:36   ` Haavard Skinnemoen

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=20060706021906.1af7ffa3.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=hskinnemoen@atmel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox