All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Xen-devel List <xen-devel@lists.xen.org>
Subject: Re: Backports for Xen 4.6
Date: Wed, 20 Jan 2016 13:14:04 +0000	[thread overview]
Message-ID: <569F881C.9060403@citrix.com> (raw)
In-Reply-To: <569F8BA002000078000C90AE@prv-mh.provo.novell.com>

On 20/01/16 12:29, Jan Beulich wrote:
>>>> On 18.01.16 at 16:53, <andrew.cooper3@citrix.com> wrote:
>> Possibly also:
>> 42940c046902 "x86/shadow: Fix missing newline in dprintk()"
> The affected statement compiles to nothing in a release build, which
> can be taken as an argument both ways. I lean towards not putting
> it in.
>
>> 6851e979874e "VT-d: use proper error codes in iommu_enable_x2apic_IR()"
> Since I had pulled this into our own tree already, and since you're
> now also viewing this as useful, I guess I will throw it in.
>
>> 0ce647ad6f70 "x86: suppress bogus log message"
> This being a purely cosmetic change, may I ask for the reason
> you consider this a backport candidate?

The shear volume reduction in debug builds.

XenServer ships both a release and a debug hypervisor for first-line
triage of customer issues.  As such, "only affecting a debug build"
isn't a relevant consideration for us, and I expect we are not alone here.

~Andrew

  reply	other threads:[~2016-01-20 13:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18 15:53 Backports for Xen 4.6 Andrew Cooper
2016-01-19 13:43 ` Ian Jackson
2016-01-19 14:24   ` Andrew Cooper
2016-01-20 12:29 ` Jan Beulich
2016-01-20 13:14   ` Andrew Cooper [this message]
2016-01-20 15:09     ` Doug Goldstein
2016-01-20 18:32 ` Andrew Cooper
2016-01-21  7:37   ` Jan Beulich

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=569F881C.9060403@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.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 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.