From: "acrux@cruxppc.org" <acrux@linuxmail.org>
To: linuxppc-dev@ozlabs.org
Subject: Re: [Linux-fbdev-devel] [PATCH] GXT400P and GXT6500P support
Date: Fri, 11 Jun 2010 06:29:29 -0700 (PDT) [thread overview]
Message-ID: <28855179.post@talk.nabble.com> (raw)
In-Reply-To: <1243903358.591.17.camel@pasglop>
Benjamin Herrenschmidt wrote:
>
> On Mon, 2009-06-01 at 09:32 +0200, Giuseppe Coviello wrote:
>
>>
>> Signed-off-by: Nico Macrionitis <acrux@cruxppc.org>
>> Signed-off-by: Giuseppe Coviello <cjg@cruxppc.org>
>
> As long as you guys have verified that it actually works, I have
> no objection.
>
> Ack.
>
> Cheers,
> Ben.
>
hi Ben,
can i ask why this patch isn't still applied?
thanks.
Nico
--
View this message in context: http://old.nabble.com/Re%3A--Linux-fbdev-devel---PATCH--GXT400P-and-GXT6500P-support-tp23811001p28855179.html
Sent from the linuxppc-dev mailing list archive at Nabble.com.
prev parent reply other threads:[~2010-06-11 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a265241c0905271157s45e23528haefbd2fa31ba6763@mail.gmail.com>
[not found] ` <20090530134236.b97158c9.krzysztof.h1@poczta.fm>
2009-06-01 7:32 ` [Linux-fbdev-devel] [PATCH] GXT400P and GXT6500P support Giuseppe Coviello
2009-06-02 0:42 ` Benjamin Herrenschmidt
2010-06-11 13:29 ` acrux@cruxppc.org [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=28855179.post@talk.nabble.com \
--to=acrux@linuxmail.org \
--cc=linuxppc-dev@ozlabs.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).