From: Ben Dooks <ben-linux@fluff.org>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: s3c-fb updates
Date: Wed, 19 May 2010 01:57:00 +0000 [thread overview]
Message-ID: <20100519015700.GE4720@trinity.fluff.org> (raw)
In-Reply-To: <AANLkTil9VFeNtsYGgUljdMo4x4McC7CA9HEcwycyXlWP@mail.gmail.com>
On Wed, May 19, 2010 at 10:53:09AM +0900, InKi Dae wrote:
> Hi, Ben
>
> I sent patch series corrected as Andrew requested yesterday.
> I was busy so I conformed your answer late.
>
> Sorry but please review my patch series again.
I've merged the 24/32BPP fix onto my tree and the window selection,
the S5PV210 shadowcon stuff is pending partly due to the fact it breaks
the build on the old hardware and secondly I'd like to put that after
the current work on multi-hardware support that was done for the s3c2443.
I've updated git.fluff.org's dev/s3c-fb branch which these and rebased
it onto the first pull set for mainline.
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
next prev parent reply other threads:[~2010-05-19 1:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 10:54 s3c-fb updates Ben Dooks
2010-05-18 10:54 ` [PATCH 1/5] s3c-fb: Change to depending on CONFIG_S3C_FB_DEV Ben Dooks
2010-05-18 10:54 ` [PATCH 2/5] s3c-fb: only init window colour key controls for windows with blending Ben Dooks
2010-05-18 10:54 ` [PATCH 3/5] s3c-fb: Initial move to unifying the header files Ben Dooks
2010-05-18 10:54 ` [PATCH 4/5] s3c-fb: udpate to support s3c2416/s3c2443 style hardware Ben Dooks
2010-05-18 10:54 ` [PATCH 5/5] s3c-fb: Integrate palette setup code into main driver Ben Dooks
2010-05-18 14:35 ` s3c-fb updates Kyungmin Park
2010-05-19 0:45 ` Ben Dooks
2010-05-19 1:53 ` InKi Dae
2010-05-19 1:57 ` Ben Dooks [this message]
2010-05-19 6:25 ` Yauhen Kharuzhy
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=20100519015700.GE4720@trinity.fluff.org \
--to=ben-linux@fluff.org \
--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).