From: Mark Rutland <mark.rutland@arm.com>
To: heiko.carstens@de.ibm.com, catalin.marinas@arm.com
Cc: linux-arch@vger.kernel.org, akpm@linux-foundation.org,
keescook@chromium.org, luto@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 0/2] THREAD_INFO_IN_TASK prep work for arm64+s390
Date: Thu, 10 Nov 2016 18:13:07 +0000 [thread overview]
Message-ID: <20161110181307.GC10137@leverpostej> (raw)
In-Reply-To: <20161102155020.GA17547@remoulade>
Hi Heiko,
On Wed, Nov 02, 2016 at 03:56:26PM +0000, Mark Rutland wrote:
> On Wed, Oct 26, 2016 at 06:43:05PM +0100, Mark Rutland wrote:
> > Heiko and I have been working on THREAD_INFO_IN_TASK for s390 and arm64
> > respectively, and we're both targetting v4.10.
> >
> > These are the common core changes which we both require. I've put together a
> > branch [1,2] based on v4.9-rc2. I intend to tag this at some point next week so
> > that Heiko and I have a stable base.
>
> As a heads-up, I've collated the tags I've received in the last few days, along
> with the comment Andy requested in the v1 thread, and tagged this as
> core-ti-stack-split [1].
>
> Thanks,
> Mark.
>
> [1] git://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git core-ti-stack-split
I believe that Catalin's hoping to take my arm64 patches for v4.10,
using the above tag as a base.
What's the plan for s390? Are you happy to do the same?
Thanks,
Mark.
next prev parent reply other threads:[~2016-11-10 18:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 17:43 [PATCHv2 0/2] THREAD_INFO_IN_TASK prep work for arm64+s390 Mark Rutland
2016-10-26 17:43 ` Mark Rutland
2016-10-26 17:43 ` [PATCHv2 1/2] thread_info: factor out restart_block Mark Rutland
2016-10-26 17:43 ` [PATCHv2 2/2] thread_info: include <current.h> for THREAD_INFO_IN_TASK Mark Rutland
2016-10-26 17:43 ` Mark Rutland
2016-11-02 15:56 ` [PATCHv2 0/2] THREAD_INFO_IN_TASK prep work for arm64+s390 Mark Rutland
2016-11-10 18:13 ` Mark Rutland [this message]
2016-11-11 9:16 ` Heiko Carstens
2016-11-11 9:16 ` Heiko Carstens
2016-11-11 15:42 ` Martin Schwidefsky
2016-11-11 15:42 ` Martin Schwidefsky
2016-11-11 16:23 ` Mark Rutland
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=20161110181307.GC10137@leverpostej \
--to=mark.rutland@arm.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=keescook@chromium.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@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).