All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: wei.liu2@citrix.com
Cc: keir@xen.org, Ian Campbell <ian.campbell@citrix.com>,
	tim@xen.org, Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Julien Grall <julien.grall@citrix.com>,
	xen-devel@lists.xenproject.org
Subject: Re: Commit moratorium
Date: Fri, 04 Sep 2015 06:08:18 -0600	[thread overview]
Message-ID: <55E9A5D2020000780009FA39@prv-mh.provo.novell.com> (raw)
In-Reply-To: <20150904115219.GR18474@zion.uk.xensource.com>

>>> On 04.09.15 at 13:52, <wei.liu2@citrix.com> wrote:
> On Fri, Sep 04, 2015 at 01:44:24AM -0600, Jan Beulich wrote:
>> >>> On 03.09.15 at 18:25, <wei.liu2@citrix.com> wrote:
>> > Xen tree is going to branch at 4.6 RC3. I don't want to branch when
>> > master != staging, so please avoid committing new patches to staging now
>> > to let master catch up with staging. Another announcement will be made
>> > when the moratorium is lifted.
>> 
>> Hmm, I think you will want to wait for a fix for the ARM64 regression
>> Julien reported before cutting RC3.
>> 
> 
> That was reported after I made this announcement.
> 
> Judging from the conversation in that thread we already have an idea
> what was broken.  Is the fix going to be complex? 

You may have seen the tentative patch meanwhile - it's a one liner.

> I think we can make the decision whether to wait for it based on it's
> complexity.
> 
> If we're sure it's not going to be too invasive, it doesn't matter if
> it's committed before or after branching because the cost of applying
> that to two trees would be minimum. Another thing I consider is that we
> want OSSTest to have a push over the weekend. With both considerations
> in mind, it would be OK if a simple patch gets committed today.

My concern is not about the need for backporting, but about the
usefulness (on ARM64) of an RC3 without that fix.

Jan

  reply	other threads:[~2015-09-04 12:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-03 16:25 Commit moratorium Wei Liu
2015-09-04  7:44 ` Jan Beulich
2015-09-04 11:52   ` Wei Liu
2015-09-04 12:08     ` Jan Beulich [this message]
2015-09-04 12:12       ` Wei Liu
2015-09-04 12:56         ` Ian Campbell
2015-09-04 13:19           ` Wei Liu
2015-09-04 14:42             ` Ian Campbell
2015-09-07 10:01 ` Wei Liu
2015-09-07 10:35   ` Ian Campbell
2015-09-24 15:37 ` Commit moratorium for possible rc4 Ian Campbell
2015-09-24 16:05   ` Wei Liu
2022-11-24  9:48 Commit moratorium Julien Grall
2022-12-01 14:32 ` Julien Grall
2022-12-01 15:17   ` Jan Beulich
2022-12-01 15:20     ` Henry Wang
2022-12-01 15:22     ` Julien Grall

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=55E9A5D2020000780009FA39@prv-mh.provo.novell.com \
    --to=jbeulich@suse.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=julien.grall@citrix.com \
    --cc=keir@xen.org \
    --cc=tim@xen.org \
    --cc=wei.liu2@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.