From: James Hogan <james.hogan@imgtec.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Mike Frysinger <vapier@gentoo.org>,
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 16:56:03 +0000 [thread overview]
Message-ID: <4F47C123.9050009@imgtec.com> (raw)
In-Reply-To: <201202241638.12205.arnd@arndb.de>
On 24/02/12 16:38, Arnd Bergmann wrote:
> On Friday 24 February 2012, Arnd Bergmann wrote:
>> We actually have MODULE_SYMBOL_PREFIX providing the correct string
>> under a name that is not appropriate here. We can probably stick with
>> Jason's patch for now and add a more sophisticated logic if another
>> user of CONFIG_SYMBOL_PREFIX comes up.
>>
>> So for Jason's patch:
>>
>> Acked-by: Arnd Bergmann <arnd@arndb.de>
>>
>> We could put that into the kernel now, but it's probably sufficient if
>> Jason keeps the patch with his others and submits it at the same time
>> when we get there.
>
> Sorry, I meant s/Jason/James/g
np. Okay, I'll keep hold of it.
Thanks
James
WARNING: multiple messages have this Message-ID (diff)
From: James Hogan <james.hogan@imgtec.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Mike Frysinger <vapier@gentoo.org>, <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 16:56:03 +0000 [thread overview]
Message-ID: <4F47C123.9050009@imgtec.com> (raw)
In-Reply-To: <201202241638.12205.arnd@arndb.de>
On 24/02/12 16:38, Arnd Bergmann wrote:
> On Friday 24 February 2012, Arnd Bergmann wrote:
>> We actually have MODULE_SYMBOL_PREFIX providing the correct string
>> under a name that is not appropriate here. We can probably stick with
>> Jason's patch for now and add a more sophisticated logic if another
>> user of CONFIG_SYMBOL_PREFIX comes up.
>>
>> So for Jason's patch:
>>
>> Acked-by: Arnd Bergmann <arnd@arndb.de>
>>
>> We could put that into the kernel now, but it's probably sufficient if
>> Jason keeps the patch with his others and submits it at the same time
>> when we get there.
>
> Sorry, I meant s/Jason/James/g
np. Okay, I'll keep hold of it.
Thanks
James
next prev parent reply other threads:[~2012-02-24 16:56 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
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 [this message]
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=4F47C123.9050009@imgtec.com \
--to=james.hogan@imgtec.com \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vapier@gentoo.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.