linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: York Sun <yorksun@freescale.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: a.p.zijlstra@chello.nl, linuxppc-dev@ozlabs.org,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: V3 Patch - Driver for Freescale 8610 and 5121 DIU
Date: Tue, 25 Mar 2008 16:27:16 -0500	[thread overview]
Message-ID: <120648043867-git-send-email-yorksun@freescale.com> (raw)


The following two patches are the 3rd version of the DIU patch for Freescale 8610 and 5121.
It fixed the issues according to the feedback from Andrew Morton.

Andrew, incremental patches are available if requested.

Regards,

York

             reply	other threads:[~2008-03-25 21:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-25 21:27 York Sun [this message]
2008-03-25 21:27 ` [PATCH 1/2 v3] Driver for Freescale 8610 and 5121 DIU York Sun
2008-03-25 21:27   ` [PATCH 2/2 v3] Add DIU platform code for MPC8610HPCD York Sun
2008-03-25 22:19   ` [PATCH 1/2 v3] Driver for Freescale 8610 and 5121 DIU Scott Wood
2008-03-27  7:54   ` Andrew Morton

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=120648043867-git-send-email-yorksun@freescale.com \
    --to=yorksun@freescale.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.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).