From: "Luis R. Rodriguez" <mcgrof@suse.com>
To: cocci@systeme.lip6.fr
Subject: Re: [PATCH v3 0/4] pci: add and use pci_ioremap_wc_bar()
Date: Tue, 26 May 2015 19:49:13 +0000 [thread overview]
Message-ID: <20150526194913.GQ23057@wotan.suse.de> (raw)
In-Reply-To: <556428E7.3050606@ti.com>
On Tue, May 26, 2015 at 11:03:51AM +0300, Tomi Valkeinen wrote:
> Hi Louis,
>
> On 21/04/15 23:20, Luis R. Rodriguez wrote:
> > From: "Luis R. Rodriguez" <mcgrof@suse.com>
> >
> > This series adds pci_ioremap_wc_bar() and makes use of it
> > on a few framebuffer device drivers.
> >
> > Luis R. Rodriguez (4):
> > pci: add pci_ioremap_wc_bar()
> > video: fbdev: i740fb: use arch_phys_wc_add() and pci_ioremap_wc_bar()
> > video: fbdev: kyrofb: use arch_phys_wc_add() and pci_ioremap_wc_bar()
> > video: fbdev: gxt4500: use pci_ioremap_wc_bar() for framebuffer
> >
> > drivers/pci/pci.c | 14 ++++++++++++++
> > drivers/video/fbdev/gxt4500.c | 2 +-
> > drivers/video/fbdev/i740fb.c | 35 ++++++-----------------------------
> > drivers/video/fbdev/kyro/fbdev.c | 33 +++++++++++----------------------
> > include/linux/pci.h | 1 +
> > include/video/kyro.h | 4 +---
> > 6 files changed, 34 insertions(+), 55 deletions(-)
>
> About this and other related series: rather than having multiple
> different patch series containing fbdev changes, going via separate
> trees, I would very much prefer to get all the requisite pci/mtrr
> related patches merged in the next merge window, and only then change
> the fbdev drivers in one series, merged via fbdev tree.
Tomi, OK, I'll ask Bjorn to drop the framebuffer driver specific changes on the
pci_iomap_wc() series then and wait until he takes only the bus specific
changes for this and the pci_iomap_wc() series. Likewise I will wait for
the x86 require changes (ioremap_uc() and pat_enabled()) stuff to be exported
before sending you the changes required for the framebuffer tree.
Luis
prev parent reply other threads:[~2015-05-26 19:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 20:20 [PATCH v3 0/4] pci: add and use pci_ioremap_wc_bar() Luis R. Rodriguez
2015-04-21 20:20 ` [PATCH v3 1/4] pci: add pci_ioremap_wc_bar() Luis R. Rodriguez
2015-05-20 21:02 ` Bjorn Helgaas
2015-05-20 21:06 ` Luis R. Rodriguez
2015-04-21 20:20 ` [PATCH v3 2/4] video: fbdev: i740fb: use arch_phys_wc_add() and pci_ioremap_wc_bar() Luis R. Rodriguez
2015-04-21 20:20 ` [PATCH v3 3/4] video: fbdev: kyrofb: " Luis R. Rodriguez
2015-04-21 20:20 ` [PATCH v3 4/4] video: fbdev: gxt4500: use pci_ioremap_wc_bar() for framebuffer Luis R. Rodriguez
2015-04-29 21:08 ` [PATCH v3 0/4] pci: add and use pci_ioremap_wc_bar() Luis R. Rodriguez
2015-05-19 17:53 ` Luis R. Rodriguez
2015-05-20 20:54 ` [Cocci] " Luis R. Rodriguez
2015-05-21 21:23 ` Luis R. Rodriguez
2015-06-16 7:15 ` Tomi Valkeinen
2015-06-16 19:05 ` Luis R. Rodriguez
2015-06-17 6:05 ` Tomi Valkeinen
2015-06-17 17:32 ` Luis R. Rodriguez
2015-05-26 8:03 ` Tomi Valkeinen
2015-05-26 19:49 ` Luis R. Rodriguez [this message]
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=20150526194913.GQ23057@wotan.suse.de \
--to=mcgrof@suse.com \
--cc=cocci@systeme.lip6.fr \
/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).