public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Jesper Nilsson <jesper.nilsson@axis.com>
Cc: Christoph Hellwig <hch@lst.de>,
	Mikael Starvik <mikael.starvik@axis.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] CRIS: Wire up syscalls signalfd4 to writev.
Date: Tue, 28 Apr 2009 18:01:07 +0200	[thread overview]
Message-ID: <20090428160107.GC26363@lst.de> (raw)
In-Reply-To: <20090428155856.GN21811@axis.com>

On Tue, Apr 28, 2009 at 05:58:56PM +0200, Jesper Nilsson wrote:
> On Mon, Apr 27, 2009 at 10:13:56AM +0200, Christoph Hellwig wrote:
> > 2.6.30 added the new preadv/pwritev system calls.  The following
> > architectures still haven't wired them up:
> > 
> > 	alpha, avr32, blackfin, cris, frv, h8300, m32r, xtensa
> > 
> > Can you maintainers please look into wiring these system calls up?
> 
> I've just added the following patch to the CRIS tree:
> 
> 
> Adds sys_signalfd4, sys_eventfd2, sys_epoll_create1, sys_dup3,
> sys_pipe2, sys_inotify_init1, sys_preadv, sys_pwritev
> for both CRISv10 and CRISv32.

Care to send this and your current stack of patches upsteam before
2.6.30 is out?


  reply	other threads:[~2009-04-28 16:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-27  8:13 missing preadv/pwritev wireup Christoph Hellwig
2009-04-27 18:26 ` [PATCH] Blackfin: hook up preadv/pwritev syscalls Mike Frysinger
2009-04-28 15:58 ` [PATCH] CRIS: Wire up syscalls signalfd4 to writev Jesper Nilsson
2009-04-28 16:01   ` Christoph Hellwig [this message]
2009-04-28 16:08     ` Jesper Nilsson

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=20090428160107.GC26363@lst.de \
    --to=hch@lst.de \
    --cc=jesper.nilsson@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikael.starvik@axis.com \
    /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