From: Jonas Bonn <jonas@southpole.se>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arch@vger.kernel.org
Subject: Re: [PATCH 1/1] Add new syscall sys_sendmmsg to generic unistd
Date: Sat, 28 May 2011 23:55:46 +0200 [thread overview]
Message-ID: <1306619746.3001.977.camel@localhost> (raw)
In-Reply-To: <201105282324.31818.arnd@arndb.de>
[-- Attachment #1: Type: text/plain, Size: 918 bytes --]
On Sat, 2011-05-28 at 23:24 +0200, Arnd Bergmann wrote:
> I just saw your git tree for the OpenRISC architecture port and it
> looks really really nice, mostly by virtue of being very small, but
> also by not copying all the things that new architecture ports normally
> get wrong at the time when they show up on my radar.
> Do you plan to submit it upstream any time soon?
Yes, it's pretty much ready for submission. There are a couple of areas
that I'm aware of that still need some work and there are some cleanups
to do, but everything that faces userspace (ABI) has settled so it's
stuff that could be done even after merging upstream.
What would be the best approach to request review? I saw that the
unicore32 architecture was posted in 'functional/subsystem' chunks... is
that the best way to do it? Shall I do the same, or do you have a
suggestion for a better way to do it?
/Jonas
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-05-28 22:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-28 20:19 [PATCH 1/1] Add new syscall sys_sendmmsg to generic unistd Jonas Bonn
2011-05-28 21:24 ` Arnd Bergmann
2011-05-28 21:55 ` Jonas Bonn [this message]
2011-05-29 18:27 ` Arnd Bergmann
2011-05-29 21:30 ` Jonas Bonn
2011-05-29 21:57 ` Arnd Bergmann
[not found] ` <tOr60tkHMHA.716@exchange1.tad.internal.tilera.com>
2011-06-01 20:15 ` 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=1306619746.3001.977.camel@localhost \
--to=jonas@southpole.se \
--cc=arnd@arndb.de \
--cc=linux-arch@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).