From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: linuxppc <linuxppc-dev@ozlabs.org>,
akonovalov@ru.mvista.com,
linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [Linux-fbdev-devel] [PATCH 0/6] Patch series to add of_platform binding to xilinxfb
Date: Tue, 9 Oct 2007 11:39:18 -0600 [thread overview]
Message-ID: <fa686aa40710091039hd945eb4n7dfdba3df37a08f2@mail.gmail.com> (raw)
In-Reply-To: <1191906242.6083.7.camel@daplas>
On 10/8/07, Antonino A. Daplas <adaplas@gmail.com> wrote:
> On Mon, 2007-10-08 at 22:43 -0600, Grant Likely wrote:
> > BTW, what path do framebuffer patches take to get into Linus' tree?
> > Does he pull your tree directly, or do they go through someone else's
> > tree?
>
> They all go to -mm tree, unless it's a needed fix, then to Linus's.
>
> Tony
Ah, okay.
Since the XilinxFB is a powerpc-only device, is it okay with you if I
get Paul Mackerras to merge them into his tree instead (that way the
changes go in with the platform code which requires these changes)
Paulus, is that okay by you?
Thanks,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2007-10-09 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071001155024.6114.47993.stgit@trillian.cg.shawcable.net>
[not found] ` <4703C8A7.8070001@ru.mvista.com>
2007-10-03 18:22 ` [PATCH 0/6] Patch series to add of_platform binding to xilinxfb Grant Likely
[not found] ` <1191370502.5238.1.camel@daplas>
[not found] ` <fa686aa40710082143k2092e7d2l35bc3bda55bb6237@mail.gmail.com>
[not found] ` <1191906242.6083.7.camel@daplas>
2007-10-09 17:39 ` Grant Likely [this message]
2007-10-09 21:06 ` [Linux-fbdev-devel] " Antonino A. Daplas
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=fa686aa40710091039hd945eb4n7dfdba3df37a08f2@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=adaplas@gmail.com \
--cc=akonovalov@ru.mvista.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).