All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: "Luis R. Rodriguez" <mcgrof@suse.com>,
	Bjorn Helgaas <bhelgaas@google.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
	Borislav Petkov <bp@suse.de>,
	linux-fbdev <linux-fbdev@vger.kernel.org>,
	"cocci@systeme.lip6.fr" <cocci@systeme.lip6.fr>,
	Andy Lutomirski <luto@amacapital.net>,
	linux-pci@vger.kernel.org
Subject: Re: [Cocci] [PATCH v3 0/4] pci: add and use pci_ioremap_wc_bar()
Date: Wed, 17 Jun 2015 06:05:54 +0000	[thread overview]
Message-ID: <55810E42.4080500@ti.com> (raw)
In-Reply-To: <20150616190504.GH11147@wotan.suse.de>

[-- Attachment #1: Type: text/plain, Size: 591 bytes --]

Hi Luis,

On 16/06/15 22:05, Luis R. Rodriguez wrote:

> Can the fbdev parts go through Bjorn's tree? We last discussed if the series
> was important to be fully merged or not by v4.2 and I recentlty provided a
> long winded review of the entire series to help maintainers pick and choose
> and decide [1].
> 
> Based on this can the fbdev patches from both of these series go through Bjorn's tree?

Yes, they can go through Bjorn's tree if there are no non-trivial
conflicts with the main fbdev stuff. linux-next should contain all the
fbdev patches going for 4.2.

 Tomi


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: "Luis R. Rodriguez" <mcgrof@suse.com>,
	Bjorn Helgaas <bhelgaas@google.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
	Borislav Petkov <bp@suse.de>,
	linux-fbdev <linux-fbdev@vger.kernel.org>,
	"cocci@systeme.lip6.fr" <cocci@systeme.lip6.fr>,
	Andy Lutomirski <luto@amacapital.net>,
	<linux-pci@vger.kernel.org>
Subject: Re: [Cocci] [PATCH v3 0/4] pci: add and use pci_ioremap_wc_bar()
Date: Wed, 17 Jun 2015 09:05:54 +0300	[thread overview]
Message-ID: <55810E42.4080500@ti.com> (raw)
In-Reply-To: <20150616190504.GH11147@wotan.suse.de>

[-- Attachment #1: Type: text/plain, Size: 591 bytes --]

Hi Luis,

On 16/06/15 22:05, Luis R. Rodriguez wrote:

> Can the fbdev parts go through Bjorn's tree? We last discussed if the series
> was important to be fully merged or not by v4.2 and I recentlty provided a
> long winded review of the entire series to help maintainers pick and choose
> and decide [1].
> 
> Based on this can the fbdev patches from both of these series go through Bjorn's tree?

Yes, they can go through Bjorn's tree if there are no non-trivial
conflicts with the main fbdev stuff. linux-next should contain all the
fbdev patches going for 4.2.

 Tomi


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-06-17  6:05 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-21 20:20 [Cocci] [PATCH v3 0/4] pci: add and use pci_ioremap_wc_bar() Luis R. Rodriguez
2015-04-21 20:20 ` Luis R. Rodriguez
2015-04-21 20:20 ` Luis R. Rodriguez
2015-04-21 20:20 ` [Cocci] [PATCH v3 1/4] pci: add pci_ioremap_wc_bar() Luis R. Rodriguez
2015-04-21 20:20   ` Luis R. Rodriguez
2015-04-21 20:20   ` Luis R. Rodriguez
2015-05-20 21:02   ` Bjorn Helgaas
2015-05-20 21:02     ` Bjorn Helgaas
2015-05-20 21:06     ` Luis R. Rodriguez
2015-05-20 21:06       ` Luis R. Rodriguez
2015-04-21 20:20 ` [Cocci] [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   ` Luis R. Rodriguez
2015-04-21 20:20   ` Luis R. Rodriguez
2015-04-21 20:20 ` [Cocci] [PATCH v3 3/4] video: fbdev: kyrofb: " Luis R. Rodriguez
2015-04-21 20:20   ` Luis R. Rodriguez
2015-04-21 20:20   ` Luis R. Rodriguez
2015-04-21 20:20 ` [Cocci] [PATCH v3 4/4] video: fbdev: gxt4500: use pci_ioremap_wc_bar() for framebuffer Luis R. Rodriguez
2015-04-21 20:20   ` Luis R. Rodriguez
2015-04-21 20:20   ` Luis R. Rodriguez
2015-04-29 21:08 ` [Cocci] [PATCH v3 0/4] pci: add and use pci_ioremap_wc_bar() Luis R. Rodriguez
2015-04-29 21:08   ` Luis R. Rodriguez
2015-05-19 17:53   ` [Cocci] " Luis R. Rodriguez
2015-05-19 17:53     ` Luis R. Rodriguez
2015-05-20 20:54     ` [Cocci] " Luis R. Rodriguez
2015-05-20 20:54       ` Luis R. Rodriguez
2015-05-21 21:23       ` 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-16 19:05           ` Luis R. Rodriguez
2015-06-16 19:05           ` Luis R. Rodriguez
2015-06-17  6:05           ` Tomi Valkeinen [this message]
2015-06-17  6:05             ` Tomi Valkeinen
2015-06-17 17:32             ` Luis R. Rodriguez
2015-06-17 17:32               ` Luis R. Rodriguez
2015-06-17 17:32               ` Luis R. Rodriguez
2015-05-26  8:03 ` Tomi Valkeinen
2015-05-26 19:49   ` [Cocci] " Luis R. Rodriguez
2015-05-26 19:49     ` Luis R. Rodriguez

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=55810E42.4080500@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=bhelgaas@google.com \
    --cc=bp@suse.de \
    --cc=cocci@systeme.lip6.fr \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mcgrof@suse.com \
    --cc=mst@redhat.com \
    --cc=plagnioj@jcrosoft.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.