From: Olaf Hering <olaf@aepfle.de>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [PATCH] linux-2.6.18/xencons: generalize use of add_preferred_console()
Date: Fri, 7 Feb 2014 13:30:17 +0100 [thread overview]
Message-ID: <20140207123017.GA31152@aepfle.de> (raw)
In-Reply-To: <52F4C280020000780011A294@nat28.tlf.novell.com>
On Fri, Feb 07, Jan Beulich wrote:
> Yes, I agree that there likely needs to be another change here.
> I'm just not certain yet which way this should be done.
Jan,
before I start doing software archaeology:
How would you want it to look like?
What combinations of Xen console= and Linux xencons=/console= are useful anyway?
Olaf
next prev parent reply other threads:[~2014-02-07 12:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 9:30 [PATCH] linux-2.6.18/xencons: generalize use of add_preferred_console() Jan Beulich
2014-02-06 22:53 ` Olaf Hering
2014-02-07 8:18 ` Jan Beulich
2014-02-07 8:32 ` Olaf Hering
2014-02-07 9:12 ` Jan Beulich
2014-02-07 10:07 ` Olaf Hering
2014-02-07 10:24 ` Jan Beulich
2014-02-07 12:30 ` Olaf Hering [this message]
2014-02-07 12:38 ` 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=20140207123017.GA31152@aepfle.de \
--to=olaf@aepfle.de \
--cc=JBeulich@suse.com \
--cc=ian.campbell@citrix.com \
--cc=xen-devel@lists.xenproject.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).