xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Dirk Behme <dirk.behme@gmx.de>, xen-devel@lists.xen.org
Cc: Dirk Behme <dirk.behme@de.bosch.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Jan Beulich <JBeulich@suse.com>,
	Dirk Behme <dirk.behme@gmail.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [PATCH] xen/arm64: Make sure we get all debug output
Date: Thu, 18 Feb 2016 10:15:53 +0000	[thread overview]
Message-ID: <1455790553.6225.14.camel@citrix.com> (raw)
In-Reply-To: <56C4A486.4000102@gmx.de>

On Wed, 2016-02-17 at 17:49 +0100, Dirk Behme wrote:
> Could this be applied, then?

Yes, sorry, this fell through the cracks somehow. I've applied it to
#staging now (from where automated testing will push it into #master).

I also added the same change to arm32/head.S and noted that I'd done so in
the commit log, I figured it would be better to avoid another RTT and
another chance to slip through the cracks to ask in advance, I hope that's
ok.

I think this would be worth backporting to 4.6 and earlier (as far back as
it applies). Jan or Ian -- would one of you mind doing so when the time
comes please? (FYI I have no other pending backports)

Ian.

  reply	other threads:[~2016-02-18 10:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-04 16:49 [PATCH] xen/arm64: Make sure we get all debug output Dirk Behme
2016-02-04 17:00 ` Ian Campbell
2016-02-04 17:07   ` Dirk Behme
2016-02-17 16:49     ` Dirk Behme
2016-02-18 10:15       ` Ian Campbell [this message]
2016-02-18 10:21         ` Jan Beulich
2016-02-19 17:13           ` Ian Jackson
2016-02-19 17:16             ` 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=1455790553.6225.14.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=dirk.behme@de.bosch.com \
    --cc=dirk.behme@gmail.com \
    --cc=dirk.behme@gmx.de \
    --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).