linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Jan Kara <jack@suse.cz>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [GIT PULL] ext4 changes for 3.15
Date: Mon, 7 Apr 2014 10:07:45 -0400	[thread overview]
Message-ID: <20140407140745.GA8855@thunk.org> (raw)
In-Reply-To: <CAJfpegv_Ng1cXbpCqicG4e3UdGK3uiDtVB4KzfRQOhDq_uhZOw@mail.gmail.com>

On Mon, Apr 07, 2014 at 03:15:36PM +0200, Miklos Szeredi wrote:
> >
> > Is there anything obvious that I might be doing wrong?
> 
> I only wired up the syscall for x86_64.   Who's responsible for adding
> all the syscall tables for the various architectures?

Ah, and I was testing with i386, not x86_64, so that it explains that.

It's been quite a while since I've worked to add a new system call,
but my impressure is that in general the person who creates the new
system call needs to reach out to the architecture maintainers
(preferably with a patch :-), since otherwise the architecture
maintainers would have no idea that a new syscall has been added.

					- Ted

  reply	other threads:[~2014-04-07 14:07 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-03 19:15 [GIT PULL] ext4 changes for 3.15 Theodore Ts'o
2014-04-03 19:39 ` Linus Torvalds
2014-04-04  3:53   ` Theodore Ts'o
2014-04-04 13:44     ` Jan Kara
2014-04-04 17:16       ` Miklos Szeredi
2014-04-04 20:23         ` Theodore Ts'o
2014-04-08 10:47           ` Dave Chinner
2014-04-04 23:43         ` Theodore Ts'o
2014-04-07 13:15           ` Miklos Szeredi
2014-04-07 14:07             ` Theodore Ts'o [this message]
2014-04-07 20:25               ` Geert Uytterhoeven
2014-04-08 11:25                 ` Heiko Carstens
2014-04-08 16:25                   ` Linus Torvalds
2014-04-08 13:47                 ` Theodore Ts'o
2014-04-09 16:40                   ` Geert Uytterhoeven
2014-04-09 16:55                     ` H. Peter Anvin
2014-04-09 17:48                       ` Geert Uytterhoeven
2014-04-09 18:23                         ` Theodore Ts'o
2014-04-09 19:19                           ` H. Peter Anvin
2014-06-24 22:03 ` Maciej W. Rozycki
2014-06-24 22:39   ` Thavatchai Makphaibulchoke
2014-06-24 23:25     ` Maciej W. Rozycki
2014-06-25 17:08     ` Linus Torvalds
2014-06-25 22:37       ` Theodore Ts'o

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=20140407140745.GA8855@thunk.org \
    --to=tytso@mit.edu \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).