From: Catalin Marinas <catalin.marinas@arm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Peter Zijlstra <peterz@infradead.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Re: ARM context switch changes for -next
Date: Wed, 4 Jan 2012 09:25:01 +0000 [thread overview]
Message-ID: <20120104092501.GI22876@arm.com> (raw)
In-Reply-To: <20120104095634.8f39a78b3ca6c85bd045bb97@canb.auug.org.au>
Hi Stephen,
On Tue, Jan 03, 2012 at 10:56:34PM +0000, Stephen Rothwell wrote:
> On Tue, 3 Jan 2012 18:14:18 +0000 Catalin Marinas <catalin.marinas@arm.com> wrote:
> > Could you please pull the branch below into -next? I'd like to give it a
> > few weeks of exposure before sending an official pull request to
> > Russell. One of the patches introduces a scheduler hook and Peter Z
> > agreed with it. You may get a conflict in -next since some scheduler
> > files have been renamed.
>
> Do you expect this to be merged by Linus during the 3.3 merge window? If
> so, it s a bit late (I expect Linus to do the 3.2 release any time). If
> not, I would like not to add it to -next until after v3.3-rc1 is released
> so that it doesn't complicate things for the merge window.
These patches are aimed for 3.4, not the upcoming merging window.
I'll ping you again after 3.3-rc1.
Thanks.
--
Catalin
prev parent reply other threads:[~2012-01-04 9:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 18:14 ARM context switch changes for -next Catalin Marinas
2012-01-03 22:56 ` Stephen Rothwell
2012-01-04 9:25 ` Catalin Marinas [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=20120104092501.GI22876@arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-next@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
/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.