xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Vijay Kilari <vijay.kilari@gmail.com>
Cc: Wei Liu <Wei.Liu2@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Prasun Kapoor <Prasun.Kapoor@caviumnetworks.com>,
	manish.jaggi@caviumnetworks.com,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Julien Grall <julien.grall@citrix.com>,
	Stefano Stabellini <stefano.stabellini@citrix.com>
Subject: Re: Requesting for freeze exception for ARM/ITS patches
Date: Tue, 14 Jul 2015 14:31:00 +0100	[thread overview]
Message-ID: <1436880660.25044.63.camel@citrix.com> (raw)
In-Reply-To: <CALicx6tVrc3YpprsPMZ8BsfgTBwXtoWihquJWSFPaoUr7ZNDwg@mail.gmail.com>

On Tue, 2015-07-14 at 15:32 +0530, Vijay Kilari wrote:
> I can fix all the required issues required for 4.6 provided if we take
> firm decision that we will have freeze exception for ITS.

_If_ v5 fixes the issues which Stefano and I have highlighted as being
required for 4.6 then I expect I would be able to support a freeze
exception for this code.

In that case I think we can take it on trust that you will fix any
remaining issues in 4.7.

In any case, even if the ITS code is not granted a freeze exception it
is still worth iterating on this code until it is such a state that it
could be committed to trunk (for 4.7) as soon as that development window
opens. Once it is ready I can keep it in my queue until the tree
reopens. So there is no need to stop development activities because of
the freeze.

Ian.


> 
> I can commit to finish/clean up any pending ITS TODO's
> 
> >
> > I have in mind some code placement which may be ok for Xen 4.6 (ITS in
> > domain_build vITS initialization directly called in the setup.c...) but it's
> > definitely against the principle that we are trying to keep the common code
> > as common as possible.
> >
> > Regards,
> >
> > --
> > Julien Grall
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  reply	other threads:[~2015-07-14 13:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-10 10:46 Requesting for freeze exception for ARM/ITS patches Vijay Kilari
2015-07-10 11:01 ` Jan Beulich
2015-07-10 15:52   ` Ian Campbell
2015-07-11  6:36     ` Julien Grall
2015-07-14  9:24       ` Vijay Kilari
2015-07-14  9:50         ` Ian Campbell
2015-07-14  9:59           ` Vijay Kilari
2015-07-10 16:07 ` Ian Campbell
2015-07-11  7:18   ` Julien Grall
2015-07-11  9:21     ` Ian Campbell
2015-07-13 21:58       ` Julien Grall
2015-07-14 10:02     ` Vijay Kilari
2015-07-14 13:31       ` Ian Campbell [this message]
2015-07-13 13:55 ` Wei Liu
2015-07-13 13:56   ` Wei Liu
2015-07-13 17:24   ` Stefano Stabellini
2015-07-13 21:50     ` Julien Grall
2015-07-14  7:49     ` Ian Campbell
2015-07-14 10:51       ` Stefano Stabellini
2015-07-16 14:08 ` Wei Liu

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=1436880660.25044.63.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Prasun.Kapoor@caviumnetworks.com \
    --cc=Wei.Liu2@citrix.com \
    --cc=julien.grall@citrix.com \
    --cc=manish.jaggi@caviumnetworks.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=vijay.kilari@gmail.com \
    --cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).