From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org,
linux-api <linux-api@vger.kernel.org>,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH v2 3/9] sparc/sparc64: allocate sys_membarrier system call number
Date: Wed, 16 Sep 2015 18:06:55 +0000 (UTC) [thread overview]
Message-ID: <558658516.9497.1442426815738.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <20150916.105720.1147038044649285686.davem@davemloft.net>
----- On Sep 16, 2015, at 1:57 PM, David Miller davem@davemloft.net wrote:
> From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> Date: Wed, 16 Sep 2015 15:05:54 +0000 (UTC)
>
>> ----- On Sep 7, 2015, at 12:15 PM, Mathieu Desnoyers
>> mathieu.desnoyers@efficios.com wrote:
>>
>>> Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
>>> Acked-by: "David S. Miller" <davem@davemloft.net>
>>> CC: Andrew Morton <akpm@linux-foundation.org>
>>> CC: linux-api@vger.kernel.org
>>> CC: sparclinux@vger.kernel.org
>>
>> Hi,
>>
>> FYI, sys_membarrier has been merged upstream in Linux 4.3-rc1. Feel free
>> to wire up this system call on sparc.
>
> Since I ACK'd this patch which wires the system call up, it should
> have been submitted by you directly. That's the whole idea.
OK, good to know. Other architecture maintainers chose to pick up the
system call wire-up patch themselves.
Andrew, can you pick up this patch please ?
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2015-09-16 18:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 16:15 [PATCH v2 0/9] Allocate sys_membarrier on main architectures Mathieu Desnoyers
2015-09-07 16:15 ` [PATCH v2 1/9] [picked] powerpc: allocate sys_membarrier system call number Mathieu Desnoyers
2015-09-07 16:15 ` [PATCH v2 2/9] mips: " Mathieu Desnoyers
2015-09-16 15:04 ` Mathieu Desnoyers
2015-09-28 17:12 ` Mathieu Desnoyers
2015-09-07 16:15 ` [PATCH v2 3/9] sparc/sparc64: " Mathieu Desnoyers
2015-09-16 15:05 ` Mathieu Desnoyers
2015-09-16 17:57 ` David Miller
2015-09-16 18:06 ` Mathieu Desnoyers [this message]
2015-09-07 16:15 ` [PATCH v2 4/9] parisc: " Mathieu Desnoyers
2015-09-16 15:07 ` Mathieu Desnoyers
2015-09-16 19:56 ` Helge Deller
2015-09-07 16:15 ` [RFC PATCH v2 5/9] alpha: " Mathieu Desnoyers
2015-09-16 15:17 ` Mathieu Desnoyers
2015-09-07 16:15 ` [RFC PATCH v2 6/9] arm: " Mathieu Desnoyers
2015-09-16 18:27 ` Mathieu Desnoyers
2015-09-17 13:13 ` Russell King - ARM Linux
2015-09-17 13:37 ` Mathieu Desnoyers
2015-09-17 13:49 ` Russell King - ARM Linux
2015-09-07 16:15 ` [RFC PATCH v2 7/9] arm64: " Mathieu Desnoyers
2015-09-16 15:18 ` Mathieu Desnoyers
2015-09-16 16:35 ` Will Deacon
2015-09-16 16:38 ` Mathieu Desnoyers
2015-09-16 16:39 ` Will Deacon
2015-09-07 16:15 ` [RFC PATCH v2 8/9] ia64: " Mathieu Desnoyers
2015-09-16 15:19 ` Mathieu Desnoyers
2015-09-07 16:15 ` [RFC PATCH v2 9/9] s390/s390x: " Mathieu Desnoyers
2015-09-16 15:20 ` Mathieu Desnoyers
2015-09-17 11:39 ` Martin Schwidefsky
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=558658516.9497.1442426815738.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).