From: Christoph Hellwig <hch@lst.de>
To: rth@twiddle.net, ink@jurassic.park.msu.ru, hskinnemoen@atmel.com,
uclinux-dist-devel@blackfin.uclinux.org, dev-etrax@axis.com,
dhowells@redhat.com, ysato@users.sourceforge.jp,
linux-m32r@ml.linux-m32r.org, chris@zankel.net
Cc: linux-kernel@vger.kernel.org
Subject: missing preadv/pwritev wireup
Date: Mon, 27 Apr 2009 10:13:56 +0200 [thread overview]
Message-ID: <20090427081356.GA32167@lst.de> (raw)
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?
next reply other threads:[~2009-04-27 8:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 8:13 Christoph Hellwig [this message]
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
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=20090427081356.GA32167@lst.de \
--to=hch@lst.de \
--cc=chris@zankel.net \
--cc=dev-etrax@axis.com \
--cc=dhowells@redhat.com \
--cc=hskinnemoen@atmel.com \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m32r@ml.linux-m32r.org \
--cc=rth@twiddle.net \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=ysato@users.sourceforge.jp \
/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