From: David Howells <dhowells@redhat.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: dhowells@redhat.com, torvalds@osdl.org,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-am33-list@redhat.com
Subject: Re: [PATCH 0/2] MN10300: Add the MN10300 architecture to Linux kernel [try #3]
Date: Thu, 08 Nov 2007 14:00:08 +0000 [thread overview]
Message-ID: <21923.1194530408@redhat.com> (raw)
In-Reply-To: <20071108041314.GG26163@stusta.de>
Adrian Bunk <bunk@kernel.org> wrote:
> The patch to include/asm-generic/Kbuild.asm doesn't seem to be required.
It is. asm/a.out.h does not exist for MN10300, therefore the export process
breaks unless it is told not to export this header. The alternative is to
move this line into each arch's individual header Kbuild file.
Whatever, I've moved this to the AOUT suppression patch as that's where it
logically belongs.
> +#elif defined(__mn10300__)
>
> Please use a CONFIG_ variable in such cases.
Done. However, I suspect these should be moved into an arch header file
somewhere.
> The parts outside arch/mn10300/ and include/asm-mn10300/ (except for the
> trivial "&& {,!}MN10300" Kconfig changes) should go separately through
> the maintainers or get ACKs from the maintainers, even more since they
> also contain cleanups like
>
> - .regions = {ERASEINFO(0x01000,64),
> + .regions = {
> + ERASEINFO(0x01000,64),
> }
I've ditched the extraneous cleanups. The jedec file needs a lot of cleanup
work anyway as it's got a lot of lines that begin with a space and a tab, but
that's outside of the scope of these patches.
I've split the addition of the jedec chip type, the fix for the net2280 driver
and the allocation of UART port types into separate patches. These can go in
advance of the main patch.
I've split the remaining MTD changes into their own patch that goes after the
main patch.
> +extern void __kprobes arch_remove_kprobe(struct kprobe *p);
I've moved that into asm-mn10300/kprobes.h.
> > A suitable toolchain can be downloaded from:
> >
> > ftp://ftp.redhat.com/pub/redhat/gnupro/AM33/
> >...
>
> What is the status of support in upstream GNU binutils and GNU gcc?
Upstream and been there for years I believe.
David
next prev parent reply other threads:[~2007-11-08 14:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 17:43 [PATCH 0/2] MN10300: Add the MN10300 architecture to Linux kernel [try #3] David Howells
2007-11-07 17:43 ` [PATCH 1/2] Suppress A.OUT library support in ELF binfmt if !CONFIG_BINFMT_AOUT " David Howells
2007-11-07 17:52 ` Mike Frysinger
2007-11-07 22:07 ` David Woodhouse
2007-11-07 23:30 ` David Howells
2007-11-07 23:54 ` Adrian Bunk
2007-11-08 4:13 ` [PATCH 0/2] MN10300: Add the MN10300 architecture to Linux kernel " Adrian Bunk
2007-11-08 14:00 ` David Howells [this message]
2007-11-09 11:02 ` Adrian Bunk
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=21923.1194530408@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=linux-am33-list@redhat.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