Linux s390 Architecture development
 help / color / mirror / Atom feed
From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Alexander Shishkin <virtuoso@slind.org>
Cc: lkml@vger.kernel.org, Martin Schwidefsky <schwidefsky@de.ibm.com>,
	linux390@de.ibm.com, Andrew Morton <akpm@linux-foundation.org>,
	Jesper Nilsson <jesper.nilsson@axis.com>,
	David Howells <dhowells@redhat.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Christoph Hellwig <hch@lst.de>,
	linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 7/7] wire up sys_time_change_notify() on s390
Date: Tue, 31 Aug 2010 14:49:28 +0200	[thread overview]
Message-ID: <20100831124928.GB2166@osiris.boeblingen.de.ibm.com> (raw)
In-Reply-To: <1283255151-6364-7-git-send-email-virtuoso@slind.org>

On Tue, Aug 31, 2010 at 02:45:51PM +0300, Alexander Shishkin wrote:
> diff --git a/arch/s390/kernel/syscalls.S b/arch/s390/kernel/syscalls.S
> index a8fee1b..b242383 100644
> --- a/arch/s390/kernel/syscalls.S
> +++ b/arch/s390/kernel/syscalls.S
> @@ -343,3 +343,4 @@ SYSCALL(sys_perf_event_open,sys_perf_event_open,sys_perf_event_open_wrapper)
>  SYSCALL(sys_fanotify_init,sys_fanotify_init,sys_fanotify_init_wrapper)
>  SYSCALL(sys_fanotify_mark,sys_fanotify_mark,sys_fanotify_mark_wrapper)
>  SYSCALL(sys_prlimit64,sys_prlimit64,sys_prlimit64_wrapper)
> +SYSCALL(sys_time_change_notify,sys_time_change_notify,sys_time_change_notify_wrapper) /* 335 */
> \ No newline at end of file

Please add the missing newline. Thanks.

  parent reply	other threads:[~2010-08-31 12:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1283255151-6364-1-git-send-email-virtuoso@slind.org>
2010-08-31 11:45 ` [PATCH 7/7] wire up sys_time_change_notify() on s390 Alexander Shishkin
2010-08-31 11:53   ` Martin Schwidefsky
2010-08-31 12:49   ` Heiko Carstens [this message]
2010-08-31 12:53     ` Alexander Shishkin
     [not found] <1284675049-23479-1-git-send-email-virtuoso@slind.org>
2010-09-16 22:10 ` Alexander Shishkin

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=20100831124928.GB2166@osiris.boeblingen.de.ibm.com \
    --to=heiko.carstens@de.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=borntraeger@de.ibm.com \
    --cc=dhowells@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=hch@lst.de \
    --cc=jesper.nilsson@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux390@de.ibm.com \
    --cc=lkml@vger.kernel.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=virtuoso@slind.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