From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: [PATCH] Enable per-VCPU parameter settings for RTDS scheduler Date: Fri, 24 Jul 2015 10:14:05 -0600 Message-ID: <55B2806D0200007800095547@prv-mh.provo.novell.com> References: <55B27BC902000078000954AF@prv-mh.provo.novell.com> <1437754162.24746.138.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1437754162.24746.138.camel@citrix.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: Chong Li , xen-devel List-Id: xen-devel@lists.xenproject.org >>> On 24.07.15 at 18:09, wrote: > On Fri, 2015-07-24 at 09:54 -0600, Jan Beulich wrote: >> considering the feature freeze you probably should be a little >> more patient (e.g. ping when the development tree re-opened). > > I don't think all 4.7 development needs to come to a halt just because we > have frozen for 4.6. Although 4.6 should be the priority, not all devs and > maintainers will be spending 100% of their time on 4.6 related stuff). > > So while maybe waiting a bit longer than usual would be good advice I don't > think waiting for the development tree to reopen is correct. > > A series can still be reviewed, revised and reposted during the freeze > until they are in a state to go in, at which point they may need to be > parked or queued until the tree reopens. Which I agree with, and which I don't think my reply excluded. Anyway - I was mainly puzzled by the ping because I had replied, without myself getting a reply... Jan