From: Eric Miao <eric.y.miao@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/8] enable pxa168 LCD on two platform
Date: Thu, 12 Nov 2009 01:05:48 +0000 [thread overview]
Message-ID: <f17812d70911111705v57317d32s3805654d9a7ff75@mail.gmail.com> (raw)
In-Reply-To: <20091111155058.4f8d355e.akpm@linux-foundation.org>
On Thu, Nov 12, 2009 at 7:50 AM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> On Tue, 10 Nov 2009 16:11:56 +0800
> Jun Nie <niej0001@gmail.com> wrote:
>
>> To: linux-arm-kernel@lists.infradead.org, linux-fbdev@vger.kernel.org
>
> I don't think linux-fbdev@vger.kernel.org exists? You wanted
> linux-fbdev-devel@lists.sourceforge.net ?
>
>> Subject: [PATCH 0/8] enable pxa168 LCD on two platform
>> Date: Tue, 10 Nov 2009 16:11:56 +0800
>> Sender: linux-fbdev-owner@vger.kernel.org
>>
>> This serial patches add LCD controller SPI support and enable frame
>> buffer on two platform. Several small fix are included.
>> comments from Eric and Russell are addressed.
>>
>>
>> arch/arm/configs/pxa168_defconfig | 86 +++++++++++++++-
>> arch/arm/configs/pxa910_defconfig | 39 +++++++-
>> arch/arm/mach-mmp/aspenite.c | 176 +++++++++++++++++++++++++++++++
>> arch/arm/mach-mmp/include/mach/pxa168.h | 8 ++
>> arch/arm/mach-mmp/include/mach/pxa910.h | 8 ++
>> arch/arm/mach-mmp/pxa168.c | 3 +
>> arch/arm/mach-mmp/pxa910.c | 4 +
>> arch/arm/mach-mmp/ttc_dkb.c | 140 ++++++++++++++++++++++++
>> drivers/gpio/pca953x.c | 1 +
>> drivers/video/pxa168fb.c | 102 ++++++++++++++++++
>> drivers/video/pxa168fb.h | 24 +----
>> include/video/pxa168fb.h | 49 ++++++++-
>> 12 files changed, 612 insertions(+), 28 deletions(-)
>
> hm. So who should review and merge these patches??
>
Hi Andrew,
I'm looking into this - actually this is the 2nd round, and I'd like
this to go through my tree since these are really pretty close to
the pxa168/910 stuff if you feel OK.
> The patches were wordwrapped by your email client. I had that all
> fixed up but the final patch gets a large number of rejects, perhaps
> against the ARM changes in linux-next so I gave up.
>
Jun,
Could you please reply each of your mail with an attachment of
the patch you formatted with 'git-format-patch'. My guess is you
are using Gmail web interface so there might be wrapping issues.
next prev parent reply other threads:[~2009-11-12 1:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 8:11 [PATCH 0/8] enable pxa168 LCD on two platform Jun Nie
2009-11-11 23:50 ` Andrew Morton
2009-11-11 23:54 ` Randy Dunlap
2009-11-12 7:47 ` Geert Uytterhoeven
2009-11-12 16:46 ` Randy Dunlap
2009-11-12 16:51 ` Geert Uytterhoeven
2009-11-12 18:22 ` Randy Dunlap
2009-11-12 1:05 ` Eric Miao [this message]
2009-11-16 9:33 ` Jun Nie
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=f17812d70911111705v57317d32s3805654d9a7ff75@mail.gmail.com \
--to=eric.y.miao@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).