From: Chris Metcalf <cmetcalf@tilera.com>
To: <linasvepstas@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
GLIBC Devel <libc-alpha@sourceware.org>,
<linux-kernel@vger.kernel.org>, <libc-ports@sourceware.org>
Subject: Re: asm-generic/unistd.h and glibc use of NR_ipc
Date: Thu, 30 Sep 2010 09:23:19 -0400 [thread overview]
Message-ID: <4CA48F47.5020101@tilera.com> (raw)
In-Reply-To: <AANLkTik4K+P_3pzN3g4_1UBnOVWTHLmRwFoHLKOS018T@mail.gmail.com>
On 9/28/2010 1:36 PM, Linas Vepstas wrote:
> On 28 September 2010 08:05, Chris Metcalf <cmetcalf@tilera.com> wrote:
>> On 9/28/2010 4:40 AM, Arnd Bergmann wrote:
>>> Chris Metcalf is using the generic unistd.h file on the tile architecture
>>> and has a glibc port that should be easily portable to all future
>>> architectures. There are a few of them getting ready to be merged
>>> now (c6x, lm32, nios2, and some people have contacted me privately
>>> for architectures I cannot name).
>>>
>> I'm happy to provide some previews of the work I'm doing to interested parties.
> Yes, this is exactly what I'm looking for! I'd love to "preview" the
> code; it'll take a good long while to get everything built and tested,
> so feeback might take a while ...
>
> Any chance that these could be split out as a distinct set of patches,
> taken apart from the tilera arch port, and submitted upstream
> independently (to glibc and/or ports collection)? I'll help w/ patch
> preparation...
At this point I'm probably a week away from having something with the
obvious bugs all fixed, at which point I can start submitting it back
upstream. The few patches I have to common infrastructure I'll just submit
to libc-alpha as git patches, then I'll probably just send a two-part patch
set to libc-ports, one with the linux/generic stuff, and one with the
tile-specific stuff. (It looks like changes are never made as "git pull"
requests on the glibc lists, just as emailed unidiffs -- someone correct me
if I'm wrong.)
Linas, if you can wait a week I'd rather have you see the stuff I believe
to be working 100% to get maximum use out of you as a reviewer :-) If you
need it sooner, of course, I'm happy to let you have something now.
--
Chris Metcalf, Tilera Corp.
http://www.tilera.com
next prev parent reply other threads:[~2010-09-30 13:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 23:26 asm-generic/unistd.h and glibc use of NR_ipc Linas Vepstas
2010-09-28 0:02 ` Mike Frysinger
2010-09-28 8:40 ` Arnd Bergmann
2010-09-28 13:05 ` Chris Metcalf
2010-09-28 15:52 ` Joseph S. Myers
2010-09-28 16:13 ` Arnd Bergmann
2010-09-28 16:41 ` Joseph S. Myers
2010-09-28 20:08 ` Arnd Bergmann
2010-09-28 16:50 ` Mike Frysinger
2010-09-28 16:42 ` Mike Frysinger
2010-09-28 16:52 ` Joseph S. Myers
2010-09-28 17:36 ` Linas Vepstas
2010-09-30 13:23 ` Chris Metcalf [this message]
2010-09-29 5:16 ` Christoph Hellwig
2010-09-29 11:55 ` Arnd Bergmann
2011-03-10 16:46 ` Linas Vepstas
2011-03-10 17:07 ` Chris Metcalf
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=4CA48F47.5020101@tilera.com \
--to=cmetcalf@tilera.com \
--cc=arnd@arndb.de \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@sourceware.org \
--cc=linasvepstas@gmail.com \
--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.