From: James Hogan <james.hogan@imgtec.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arch@vger.kernel.org, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] [PATCH] asm-generic/unistd.h: handle symbol prefixes in cond_syscall
Date: Fri, 24 Feb 2012 15:40:18 +0000 [thread overview]
Message-ID: <4F47AF62.10507@imgtec.com> (raw)
In-Reply-To: <201202241509.41809.arnd@arndb.de>
On 24/02/12 15:09, Arnd Bergmann wrote:
> On Friday 24 February 2012, James Hogan wrote:
>> I've been looking at your initial comments for other architecture
>> submissions and they've been very helpful, but if you do have any
>> arch/metag specific suggestions I'd certainly welcome them.
>
> I've had only a brief look. In general I recommend doing whatever
> openrisc does, they are currently the best implementation we have.
Okay, thanks for the tip.
> In order to get the code merged, you will need to move probing
> of on-chip buses to device trees rather than hardcoding the
> platform devices, that is probably the largest amount of work
> that is still needed unless you've done that already in a later
> version.
Okay, this is something I've been looking at.
> Do you have a git tree or patch with the latest source code?
> the only copy I could find is a 2.6.37 kernel inside of a huge
> tarball.
Sorry, but unfortunately that's the latest released version of the
kernel and I can't publish anything more recent at the moment.
Thanks
James
WARNING: multiple messages have this Message-ID (diff)
From: James Hogan <james.hogan@imgtec.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: <linux-arch@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] [PATCH] asm-generic/unistd.h: handle symbol prefixes in cond_syscall
Date: Fri, 24 Feb 2012 15:40:18 +0000 [thread overview]
Message-ID: <4F47AF62.10507@imgtec.com> (raw)
In-Reply-To: <201202241509.41809.arnd@arndb.de>
On 24/02/12 15:09, Arnd Bergmann wrote:
> On Friday 24 February 2012, James Hogan wrote:
>> I've been looking at your initial comments for other architecture
>> submissions and they've been very helpful, but if you do have any
>> arch/metag specific suggestions I'd certainly welcome them.
>
> I've had only a brief look. In general I recommend doing whatever
> openrisc does, they are currently the best implementation we have.
Okay, thanks for the tip.
> In order to get the code merged, you will need to move probing
> of on-chip buses to device trees rather than hardcoding the
> platform devices, that is probably the largest amount of work
> that is still needed unless you've done that already in a later
> version.
Okay, this is something I've been looking at.
> Do you have a git tree or patch with the latest source code?
> the only copy I could find is a 2.6.37 kernel inside of a huge
> tarball.
Sorry, but unfortunately that's the latest released version of the
kernel and I can't publish anything more recent at the moment.
Thanks
James
next prev parent reply other threads:[~2012-02-24 15:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 14:01 [RFC] [PATCH] asm-generic/unistd.h: handle symbol prefixes in cond_syscall James Hogan
2012-02-24 14:01 ` James Hogan
2012-02-24 14:23 ` Arnd Bergmann
2012-02-24 14:24 ` Arnd Bergmann
2012-02-24 14:51 ` James Hogan
2012-02-24 14:51 ` James Hogan
2012-02-24 15:09 ` Arnd Bergmann
2012-02-24 15:40 ` James Hogan [this message]
2012-02-24 15:40 ` James Hogan
2012-02-24 16:19 ` Mike Frysinger
2012-02-24 16:37 ` Arnd Bergmann
2012-02-24 16:38 ` Arnd Bergmann
2012-02-24 16:56 ` James Hogan
2012-02-24 16:56 ` James Hogan
2012-02-24 16:41 ` Mike Frysinger
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=4F47AF62.10507@imgtec.com \
--to=james.hogan@imgtec.com \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@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.