From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Alexander Shishkin <virtuoso@slind.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Howells <dhowells@redhat.com>,
Christoph Hellwig <hch@lst.de>, "H. Peter Anvin" <hpa@zytor.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/7] wire up sys_time_change_notify() on ARM
Date: Wed, 1 Sep 2010 10:14:55 +0100 [thread overview]
Message-ID: <20100901091455.GL8142@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1283255151-6364-2-git-send-email-virtuoso@slind.org>
On Tue, Aug 31, 2010 at 02:45:46PM +0300, Alexander Shishkin wrote:
> sys_time_change_notify() is a new syscall with number and types of
> parameters such that no ARM-specific processing is needed.
This patch needs to be redone. Please wait until I've finished catching
up with the last 10 or so days of email and merged my tree into mainline.
Alternatively, update your patch to apply on top of my master branch.
next prev parent reply other threads:[~2010-09-01 9:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 11:45 [PATCH 1/7] [RFCv4] notify userspace about time changes Alexander Shishkin
2010-08-31 11:45 ` [PATCH 2/7] wire up sys_time_change_notify() on ARM Alexander Shishkin
2010-08-31 12:37 ` Mikael Pettersson
2010-08-31 12:42 ` Alexander Shishkin
2010-09-01 9:14 ` Russell King - ARM Linux [this message]
2010-09-01 11:02 ` Alexander Shishkin
2010-08-31 11:45 ` [PATCH 6/7] wire up sys_time_change_notify() on ia64 Alexander Shishkin
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
2010-08-31 12:53 ` Alexander Shishkin
2010-09-16 22:10 [PATCHv5 0/7] system time changes notification Alexander Shishkin
2010-09-16 22:10 ` [PATCH 2/7] wire up sys_time_change_notify() on ARM 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=20100901091455.GL8142@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=hch@lst.de \
--cc=hpa@zytor.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®