public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Michael Ellerman <mpe@ellerman•id.au>
Cc: Kees Cook <keescook@google•com>,
	Benjamin Herrenschmidt <benh@kernel•crashing.org>,
	linuxppc-dev@lists•ozlabs.org, linux-next@vger•kernel.org,
	linux-kernel@vger•kernel.org,
	Christophe Leroy <christophe.leroy@c-s•fr>,
	"oss@buserror•net" <oss@buserror•net>
Subject: Re: linux-next: manual merge of the kspp tree with the powerpc tree
Date: Mon, 18 Jul 2016 22:19:49 +1000	[thread overview]
Message-ID: <20160718221949.620fba2c@canb.auug.org.au> (raw)
In-Reply-To: <871t2rb496.fsf@@concordia.ellerman.id.au>

Hi Michael,

On Mon, 18 Jul 2016 21:00:05 +1000 Michael Ellerman <mpe@ellerman•id.au> wrote:
>
> Stephen Rothwell <sfr@canb•auug.org.au> writes:
> 
> > from the powerpc tree and commit:  
> 
> Actually that's in Scott's tree.

Oops, sorry.

> > Michael: time to sort these selects?  
> 
> Yeah I was thinking that the other day. Not sure when is a good time though.

Just after -rc1, before you open the powerpc tree up again so most of
the powerpc patches can be based after it.  Also a good time to update
the config files if necessary.

-- 
Cheers,
Stephen Rothwell

      parent reply	other threads:[~2016-07-18 12:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-18  3:03 linux-next: manual merge of the kspp tree with the powerpc tree Stephen Rothwell
2016-07-18 11:00 ` Michael Ellerman
2016-07-18 11:00 ` Michael Ellerman
     [not found] ` <871t2rb496.fsf@@concordia.ellerman.id.au>
2016-07-18 12:19   ` Stephen Rothwell [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=20160718221949.620fba2c@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=benh@kernel$(echo .)crashing.org \
    --cc=christophe.leroy@c-s$(echo .)fr \
    --cc=keescook@google$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=mpe@ellerman$(echo .)id.au \
    --cc=oss@buserror$(echo .)net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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