From: Catalin Marinas <catalin.marinas@arm.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [RFC][CFT][CFReview] execve and kernel_thread unification work
Date: Wed, 17 Oct 2012 17:40:35 +0100 [thread overview]
Message-ID: <20121017164035.GE27870@arm.com> (raw)
In-Reply-To: <20121017163424.GA2616@ZenIV.linux.org.uk>
On Wed, Oct 17, 2012 at 05:34:24PM +0100, Al Viro wrote:
> On Wed, Oct 17, 2012 at 03:02:15PM +0100, Catalin Marinas wrote:
> > Hi Al,
> >
> > On 15 October 2012 02:30, Al Viro <viro@zeniv.linux.org.uk> wrote:
> > > arch-arm64 - patches from maintainer with minor followup folded
> >
> > Thanks for updating the arm64 branch. I've adapted the changes, tested
> > and folded them into the branch below (the AArch64 instruction set
> > does not have conditional instructions):
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/cmarinas/linux-aarch64.git
> > execve
>
> Fetched and merged, thanks. I'll probably drop arch-arm64 branch, now
> that I have yours directly merged. In any case, right now arch-arm64
> points to the current head or yours and for-next has
>
> commit 0cea479343cbfaec3a9b8accdeadae53322d98a8
> Merge: 43cc05a 6a87277
> Author: Al Viro <viro@zeniv.linux.org.uk>
> Date: Wed Oct 17 12:29:32 2012 -0400
>
> Merge branch 'execve' of git://git.kernel.org/pub/scm/linux/kernel/git/cmarinas/linux-aarch
>
> in it...
Sounds fine. Thanks.
--
Catalin
next prev parent reply other threads:[~2012-10-17 16:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 21:38 [RFC][CFT][CFReview] execve and kernel_thread unification work Al Viro
2012-10-05 16:07 ` Catalin Marinas
2012-10-06 16:19 ` Al Viro
2012-10-09 19:48 ` Chris Metcalf
2012-10-09 19:48 ` Chris Metcalf
2012-10-10 4:51 ` Al Viro
2012-10-11 9:00 ` Paul Mackerras
2012-10-11 12:53 ` Al Viro
2012-10-12 0:16 ` Paul Mackerras
2012-10-12 1:09 ` [git pull] signal.git, pile 2 (was Re: [RFC][CFT][CFReview] execve and kernel_thread unification work) Al Viro
2012-10-12 5:32 ` Paul Mackerras
2012-10-12 7:55 ` Benjamin Herrenschmidt
2012-10-15 1:30 ` [RFC][CFT][CFReview] execve and kernel_thread unification work Al Viro
2012-10-17 6:16 ` Greg Ungerer
2012-10-17 6:16 ` Greg Ungerer
2012-10-17 14:02 ` Catalin Marinas
2012-10-17 16:34 ` Al Viro
2012-10-17 16:40 ` Catalin Marinas [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-01 21:34 Al Viro
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=20121017164035.GE27870@arm.com \
--to=catalin.marinas@arm.com \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.