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: Boris Derzhavets <bderzhavets@yahoo.com>,
	xen-devel@lists.xensource.com,
	Andy Georges <andy.georges@elis.ugent.be>
Subject: Re: Patch for 2.6.31-rc9
Date: Tue, 22 Sep 2009 15:24:51 -0400	[thread overview]
Message-ID: <20090922192451.GA31927@phenom.dumpdata.com> (raw)
In-Reply-To: <4AB90AE2.4050900@goop.org>

On Tue, Sep 22, 2009 at 10:35:30AM -0700, Jeremy Fitzhardinge wrote:
> On 09/22/09 08:14, Boris Derzhavets wrote:
> > This seems a kind of mystery for me. Message from Jeremy (@xen-devel)
> > , suggesting to add "# <linux/dma-mapping.h>"  to file
> > "include/linux/swiotlb.h"  was made about 2-3 weeks ago. Since then
> > kernel's git repo got a lot of commits, moved to 2.6.31. Swiotlb issue
> > was tracked down and fixed by Konrad and etc.
> > However, include/linux/swiotlb.h stays the same.
> >
> 
> Sorry about that.  I have been meaning to ask for a .config which shows
> this compile problem so I can verify the fix (I want to check what
> combination of CONFIG_ options causes/avoids the problem).

CONFIG_DRM=y
CONFIG_DRM_TTM=m

> 
> Thanks,
>     J
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  reply	other threads:[~2009-09-22 19:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-22 14:55 Patch for 2.6.31-rc9 Andy Georges
2009-09-22 15:14 ` Boris Derzhavets
2009-09-22 17:35   ` Jeremy Fitzhardinge
2009-09-22 19:24     ` Konrad Rzeszutek Wilk [this message]
2009-09-22 22:14       ` Jeremy Fitzhardinge
2009-09-23  4:46         ` Boris Derzhavets
2009-09-23 19:05           ` Jeremy Fitzhardinge
2009-09-23 19:20             ` Boris Derzhavets

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=20090922192451.GA31927@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=andy.georges@elis.ugent.be \
    --cc=bderzhavets@yahoo.com \
    --cc=jeremy@goop.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.