From: "Jan Beulich" <JBeulich@suse.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: preparing for 4.5.1
Date: Mon, 13 Apr 2015 09:35:10 +0100 [thread overview]
Message-ID: <552B9BDE020000780007158A@mail.emea.novell.com> (raw)
In-Reply-To: <1427968916.4037.32.camel@citrix.com>
>>> On 02.04.15 at 12:01, <ian.campbell@citrix.com> wrote:
> On Thu, 2015-03-26 at 17:07 +0000, Jan Beulich wrote:
>> having been released mid January, it is time to get ready for 4.5.1-rc1.
>> Please reply with backport requests which you consider necessary but
>> still missing. Please also be patient with them being pulled in - I'll be
>> gone the coming two weeks, and I'd hope to get an RC1 put together
>> soon thereafter.
>
> On my list for ARM I have this patch, which also touches x86. What do
> you think?
If it fixes a real problem in 4.5 (rather than just a theoretical one,
exposed only in 4.6), then I'm fine with this (and assume since it's
mostly for ARM you'll take care of doing and applying the backport).
Jan
next prev parent reply other threads:[~2015-04-13 8:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 17:07 preparing for 4.5.1 Jan Beulich
2015-03-26 17:19 ` Andrew Cooper
2015-03-30 10:24 ` preparing for 4.5.1 (ARM) Ian Campbell
2015-03-30 12:04 ` Julien Grall
2015-03-30 12:57 ` preparing for 4.5.1 Wei Liu
2015-04-02 0:48 ` Jim Fehlig
2015-03-30 13:15 ` Roger Pau Monné
2015-03-30 14:07 ` Julien Grall
2015-04-13 8:36 ` Jan Beulich
2015-04-13 9:05 ` Andrew Cooper
2015-04-02 10:01 ` Ian Campbell
2015-04-13 8:35 ` Jan Beulich [this message]
2015-04-14 13:12 ` Ian Campbell
2015-04-14 13:55 ` Vijay Kilari
2015-04-14 14:09 ` Ian Campbell
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=552B9BDE020000780007158A@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=ian.campbell@citrix.com \
--cc=xen-devel@lists.xenproject.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.