[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1433436288-16792-1-git-send-email-mcgrof@do-not-panic.com>
Date: Thu, 4 Jun 2015 09:44:45 -0700
From: "Luis R. Rodriguez" <mcgrof@...not-panic.com>
To: tomi.valkeinen@...com
Cc: plagnioj@...osoft.com, bp@...e.de, hpa@...or.com,
linux-fbdev@...r.kernel.org, luto@...capital.net,
toshi.kani@...com, sbsiddha@...il.com, mingo@...e.hu,
tglx@...utronix.de, jgross@...e.com, daniel.vetter@...ll.ch,
airlied@...hat.com, adaplas@...il.com, robdclark@...il.com,
jg1.han@...sung.com, wsa@...-dreams.de,
linux-kernel@...r.kernel.org, "Luis R. Rodriguez" <mcgrof@...e.com>
Subject: [PATCH v4 0/3] vesafb: remove theoretical MTRR uses
From: "Luis R. Rodriguez" <mcgrof@...e.com>
Tomi,
This v4 fixes the issue of the use of the old use of
info->par for the pseudo_palette and our need to extend
it for the MTRR cookie by extending our proposed new
struct vesafb_par with the pseudo_palette and later
pointing info->pseudo_palette to it. This also means
we can simplify the allocation of the info when calling
framebuffer_alloc() by now just passing the size of our
struct vesafb_par.
Patch 1 is unmodified from v3 series, patch 2 does the
fixes mentioned above, and patch 3 might have small
changes to account for contextual changes.
Luis R. Rodriguez (3):
video: fbdev: vesafb: only support MTRR_TYPE_WRCOMB
video: fbdev: vesafb: add missing mtrr_del() for added MTRR
video: fbdev: vesafb: use arch_phys_wc_add()
drivers/video/fbdev/vesafb.c | 80 ++++++++++++++++----------------------------
1 file changed, 28 insertions(+), 52 deletions(-)
--
2.3.2.209.gd67f9d5.dirty
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists