From: "Luis R. Rodriguez" <mcgrof@suse.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"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 19:32:26 +0200 [thread overview]
Message-ID: <20150617173226.GI11147@wotan.suse.de> (raw)
In-Reply-To: <55810E42.4080500@ti.com>
On Wed, Jun 17, 2015 at 09:05:54AM +0300, Tomi Valkeinen wrote:
> 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.
Great, thanks Tomi.
Luis
prev parent reply other threads:[~2015-06-17 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1429647634-17169-1-git-send-email-mcgrof@do-not-panic.com>
[not found] ` <CAB=NE6VYvd-Au58QRJprCquuvJkY9NYe1x8FmbW7qAhVrVE=QQ@mail.gmail.com>
[not found] ` <20150519175310.GH23057@wotan.suse.de>
[not found] ` <CAB=NE6UsMMoPhkKof+VN7ZUCd81VxrwP9nqHDUj5Lr3DJLm3bA@mail.gmail.com>
[not found] ` <CAB=NE6UdW2d6zO1hYbTnPcoZWt8+Yg5KdWE_bdqAuR_ysey_+A@mail.gmail.com>
[not found] ` <557FCD1A.4020105@ti.com>
2015-06-16 19:05 ` [Cocci] [PATCH v3 0/4] pci: add and use pci_ioremap_wc_bar() Luis R. Rodriguez
2015-06-17 6:05 ` Tomi Valkeinen
2015-06-17 17:32 ` 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=20150617173226.GI11147@wotan.suse.de \
--to=mcgrof@suse.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=mst@redhat.com \
--cc=plagnioj@jcrosoft.com \
--cc=tomi.valkeinen@ti.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 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).