From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: jayakumar.lkml@gmail.com, damm@opensource.se,
linux-kernel@vger.kernel.org, armbru@redhat.com
Subject: Re: [PATCH 1/3] fb-defio: If FBINFO_VIRTFB is defined, do not set VM_IO flag.
Date: Thu, 03 Dec 2009 11:05:34 -0800 [thread overview]
Message-ID: <4B180BFE.1000903@goop.org> (raw)
In-Reply-To: <20091203185606.GB17342@phenom.dumpdata.com>
On 12/03/09 10:56, Konrad Rzeszutek Wilk wrote:
> On Thu, Dec 03, 2009 at 10:50:15AM -0800, Jeremy Fitzhardinge wrote:
>
>> On 12/03/09 07:31, Konrad Rzeszutek Wilk wrote:
>>
>>> Most users (except sh_mobile_lcdcfb.c) get their framebuffer from
>>> vmalloc. Setting VM_IO is not necessary as the memory obtained
>>> from vmalloc is System RAM type and is not susceptible to PCI memory
>>> constraints.
>>>
>>>
>> Looks good, but you forgot signoffs on these. Do you want me to add them?
>>
> Duh!! Please do. Thank you for noticing it.
>
Already done ;) Will merge into xen/master shortly. I'd like to queue
this up for this merge window if Jaya is OK with it, and also mark for
stable. Though I think fbdev overall is currently considered
maintainerless...
J
next prev parent reply other threads:[~2009-12-03 19:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 15:31 [PATCH] fb-defio: Inhibit setting VM_IO flag if FBINFO_VIRTFB is set Konrad Rzeszutek Wilk
2009-12-03 15:31 ` [PATCH 1/3] fb-defio: If FBINFO_VIRTFB is defined, do not set VM_IO flag Konrad Rzeszutek Wilk
2009-12-03 15:31 ` [PATCH 2/3] xen pvfb: Inhibit VM_IO flag to be set on vmalloc-ed framebuffers Konrad Rzeszutek Wilk
2009-12-03 15:31 ` [PATCH 3/3] fb-defio: " Konrad Rzeszutek Wilk
2009-12-04 0:35 ` Jaya Kumar
2009-12-04 0:52 ` Jeremy Fitzhardinge
2009-12-04 1:13 ` Jaya Kumar
2009-12-03 18:50 ` [PATCH 1/3] fb-defio: If FBINFO_VIRTFB is defined, do not set VM_IO flag Jeremy Fitzhardinge
2009-12-03 18:56 ` Konrad Rzeszutek Wilk
2009-12-03 19:05 ` Jeremy Fitzhardinge [this message]
2009-12-04 0:34 ` Jaya Kumar
2009-12-04 7:42 ` Magnus Damm
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=4B180BFE.1000903@goop.org \
--to=jeremy@goop.org \
--cc=armbru@redhat.com \
--cc=damm@opensource.se \
--cc=jayakumar.lkml@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.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