All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: linux-kernel@vger.kernel.org, heiko.carstens@de.ibm.com
Cc: linux-arch@vger.kernel.org, akpm@linux-foundation.org,
	keescook@chromium.org, luto@kernel.org
Subject: Re: [PATCHv2 0/2] THREAD_INFO_IN_TASK prep work for arm64+s390
Date: Wed, 2 Nov 2016 15:56:27 +0000	[thread overview]
Message-ID: <20161102155020.GA17547@remoulade> (raw)
In-Reply-To: <1477503787-25537-1-git-send-email-mark.rutland@arm.com>

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

  parent reply	other threads:[~2016-11-02 15:56 UTC|newest]

Thread overview: 9+ 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 ` [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-11-02 15:56 ` Mark Rutland [this message]
2016-11-10 18:13   ` [PATCHv2 0/2] THREAD_INFO_IN_TASK prep work for arm64+s390 Mark Rutland
2016-11-11  9:16     ` Heiko Carstens
2016-11-11 15:42       ` Martin Schwidefsky
2016-11-11 16:23         ` Mark Rutland
  -- strict thread matches above, loose matches on Subject: below --
2016-10-26 17:42 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=20161102155020.GA17547@remoulade \
    --to=mark.rutland@arm.com \
    --cc=akpm@linux-foundation.org \
    --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 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.