From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Roberto Luongo <rluongo@ready.it>,
Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] AMD/guest_iommu: Disable guest iommu support
Date: Thu, 2 Oct 2014 11:16:57 -0400 [thread overview]
Message-ID: <20141002151657.GE32249@laptop.dumpdata.com> (raw)
In-Reply-To: <542D8246020000780003C0E1@mail.emea.novell.com>
On Thu, Oct 02, 2014 at 03:50:14PM +0100, Jan Beulich wrote:
> >>> On 02.10.14 at 16:08, <andrew.cooper3@citrix.com> wrote:
> > I forgot to explicitly indicate, but this is a bugfix and is therefore
> > intended for inclusion in 4.5
>
> And I continue to think that this also isn't necessary until pretty
> late in the release process. We really need this indication for late
> features coming in.
I am OK with bugfixes being added in before RC0 without having to
rubber-stamp them (as surely the maintainers know best whether the
bug-fix should go in or not).
But after RC0 I believe it makes sense to take a step to figure out the
regression factor (if any).
>
> Jan
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-10-02 15:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 14:02 [PATCH] AMD/guest_iommu: Disable guest iommu support Andrew Cooper
2014-10-02 14:08 ` Andrew Cooper
2014-10-02 14:50 ` Jan Beulich
2014-10-02 15:16 ` Konrad Rzeszutek Wilk [this message]
2014-10-06 6:46 ` Suravee Suthikulpanit
2014-10-06 7:59 ` Jan Beulich
2014-10-06 9:11 ` Andrew Cooper
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=20141002151657.GE32249@laptop.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Aravind.Gopalakrishnan@amd.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=rluongo@ready.it \
--cc=suravee.suthikulpanit@amd.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).