From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Andrew Jones <drjones@redhat.com>,
xen-devel@lists.xensource.com, FlorianSchandinat@gmx.de,
jeremy@goop.org, virtualization@lists.linux-foundation.org,
Konrad Rzeszutek Wilk <konrad@darnok.org>
Subject: Re: [Xen-devel] [PATCH 2/4 v2] xen kconfig: relax INPUT_XEN_KBDDEV_FRONTEND deps
Date: Thu, 15 Mar 2012 23:24:28 -0700 [thread overview]
Message-ID: <20120316062428.GA16291@core.coreip.homeip.net> (raw)
In-Reply-To: <20120315172305.GA32759@phenom.dumpdata.com>
On Thu, Mar 15, 2012 at 01:23:05PM -0400, Konrad Rzeszutek Wilk wrote:
> On Wed, Jan 11, 2012 at 11:29:20AM -0500, Andrew Jones wrote:
> >
> >
> > ----- Original Message -----
> > > On Mon, Jan 09, 2012 at 06:51:41PM +0100, Andrew Jones wrote:
> > > > PV-on-HVM guests may want to use the xen keyboard/mouse frontend,
> > > > but
> > > > they don't use the xen frame buffer frontend. For this case it
> > > > doesn't
> > >
> > > Ok, but PV does?
> > > > make much sense for INPUT_XEN_KBDDEV_FRONTEND to depend on
> > > > XEN_FBDEV_FRONTEND. The opposite direction always makes more sense,
> > > > i.e.
> > > > if you're using xenfb, then you'll want xenkbd. Switch the
> > > > dependencies.
> > >
> > > That sounds like it would be universal irregardless if it is
> > > PV or PVonHVM?
> >
> > This patch makes it such that if you want to use both, then you must
> > select both. It also says that if you want FB, then you need the
> > KBD. However, if you only want the KBD then you're fine with just
> > that. So there isn't any risk of breaking configs designed to use
> > FB, because FB should be manually selected for those configs anyway.
>
> Dmitry,
>
> I am OK with this patch. Should I pick it up on my tree for 3.4 or
> are you OK doing it via your tree?
Konrad,
I don't have a good copy of the patch so it you could pick it up that
would be great.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2012-03-16 6:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120109075911.GA4049@core.coreip.homeip.net>
2012-01-09 10:43 ` [Xen-devel] [PATCH 2/4] xen kconfig: relax INPUT_XEN_KBDDEV_FRONTEND deps Andrew Jones
2012-01-09 17:51 ` [PATCH 2/4 v2] " Andrew Jones
2012-01-11 16:11 ` [Xen-devel] " Konrad Rzeszutek Wilk
2012-01-11 16:29 ` Andrew Jones
2012-03-15 17:23 ` Konrad Rzeszutek Wilk
2012-03-16 6:24 ` Dmitry Torokhov [this message]
2012-03-16 14:48 ` Konrad Rzeszutek Wilk
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=20120316062428.GA16291@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=FlorianSchandinat@gmx.de \
--cc=drjones@redhat.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=konrad@darnok.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=xen-devel@lists.xensource.com \
/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).