From: Al Viro <viro@ZenIV.linux.org.uk>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: czankel <chris@zankel.net>,
linux-arch@vger.kernel.org, Marc Gauthier <marc@tensilica.com>
Subject: Re: [PATCH v2 0/4] xtensa: conversion to generic kernel_thread and friends
Date: Mon, 29 Oct 2012 18:11:56 +0000 [thread overview]
Message-ID: <20121029181156.GZ2616@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAMo8BfKUDHyMjDRUO8jRJ=RFWcsasXKe0_Rr88+xjLkkzTa_Ng@mail.gmail.com>
On Mon, Oct 29, 2012 at 07:58:02PM +0300, Max Filippov wrote:
> On Mon, Oct 29, 2012 at 8:23 PM, czankel <chris@zankel.net> wrote:
> > Hi Max,
> >
> > Has anything changed from the version that's already in linux-next? I wanted
> > to push that version upstream today.
>
> It's the same. I sent self-contained series to Al in case it blocks whatever.
I'd very much prefer to pull from xtensa tree, to avoid the PITA with
merge conflicts later. It's your current #for_next, right? And there's
not much besides those commits in there, so I'm grabbing that one...
prev parent reply other threads:[~2012-10-29 18:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 14:56 [PATCH v2 0/4] xtensa: conversion to generic kernel_thread and friends Max Filippov
2012-10-29 14:56 ` [PATCH v2 1/4] xtensa: reset windowbase/windowstart when cloning the VM Max Filippov
2012-10-29 16:10 ` Marc Gauthier
2012-10-29 14:56 ` [PATCH v2 2/4] xtensa: switch to generic kernel_thread() Max Filippov
2012-10-29 14:56 ` [PATCH v2 3/4] xtensa: switch to generic kernel_execve() Max Filippov
2012-10-29 14:56 ` [PATCH v2 4/4] xtensa: switch to generic sys_execve() Max Filippov
2012-10-29 16:23 ` [PATCH v2 0/4] xtensa: conversion to generic kernel_thread and friends czankel
2012-10-29 16:58 ` Max Filippov
2012-10-29 18:11 ` Al Viro [this message]
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=20121029181156.GZ2616@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=chris@zankel.net \
--cc=jcmvbkbc@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=marc@tensilica.com \
/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.