All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Bastian Blank <waldi@debian.org>, xen-devel@lists.xensource.com
Subject: Re: [PATCH] xen: fbdev frontend needs xenbus frontend
Date: Thu, 25 Feb 2010 12:48:08 -0500	[thread overview]
Message-ID: <20100225174808.GB13270@phenom.dumpdata.com> (raw)
In-Reply-To: <4B86B562.4030009@goop.org>

On Thu, Feb 25, 2010 at 09:37:38AM -0800, Jeremy Fitzhardinge wrote:
> On 02/25/2010 04:40 AM, Konrad Rzeszutek Wilk wrote:
>> On Wed, Feb 24, 2010 at 02:58:28PM +0100, Bastian Blank wrote:
>>    
>>> The fbdev (and kbddev) frontend needs the xenbus frontend, but does not
>>> define a dependency.  Make the fbdev frontend select the xenbus
>>> frontend.
>>>      
>> Isn't this the same as ba69ea42f8ba8286cbe0e939bd1ce781b7905b84? If so
>> (and if the above mention commit isn't in xen/next)
>> shouldn't you also make this change for drives/input/Kconfig for
>> XEN_KBDDEV_FRONTEND?
>>    
>
> Did that end up in .33?  Should we put it in -stable too?


I took a look at the code and I think Bastian's is OK. The -stable
has this:

152 config XEN_KBDDEV_FRONTEND
153         tristate "Xen virtual keyboard and mouse support"
154         depends on XEN_FBDEV_FRONTEND
155         default y

So it would end up selecting the xenbus frontend as well with Bastian's
patch.

  reply	other threads:[~2010-02-25 17:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24 13:58 [PATCH] xen: fbdev frontend needs xenbus frontend Bastian Blank
2010-02-25 12:40 ` Konrad Rzeszutek Wilk
2010-02-25 17:37   ` Jeremy Fitzhardinge
2010-02-25 17:48     ` Konrad Rzeszutek Wilk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-10-04 18:30 [PATCH] xen: Disable stack protector for irq helper Bastian Blank
2009-10-04 23:06 ` Jeremy Fitzhardinge
2009-10-05  1:52   ` [PATCH] xen: fbdev frontend needs xenbus frontend Bastian Blank

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=20100225174808.GB13270@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=jeremy@goop.org \
    --cc=waldi@debian.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 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.