From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/9] PXA: pxafb: Add ACX517AKN support
Date: Tue, 10 Aug 2010 23:45:05 +0200 [thread overview]
Message-ID: <20100810214505.876721536EF@gemini.denx.de> (raw)
In-Reply-To: <1281415810-31363-2-git-send-email-marek.vasut@gmail.com>
Dear Marek Vasut,
In message <1281415810-31363-2-git-send-email-marek.vasut@gmail.com> you wrote:
> ACX517AKN LCD panel is found in Palm Tungsten|C
>
> Signed-off-by: Marek Vasut <marek.vasut@gmail.com>
> ---
> arch/arm/cpu/pxa/pxafb.c | 34 ++++++++++++++++++++++++++++++++++
> 1 files changed, 34 insertions(+), 0 deletions(-)
This is a resubmission, right?
Why do you not mark the patch version in the subject,
like "[PATCH 2/9 v2]" or so?
And why is there no thread information present? (i. e. why are the
In-reply-to: and References: headers not set to point to the previous
versions of the patch?)
And why did you not include any information what has been changed
between the previous version and this one?
I do not intend to run diff over your patches.
Please document your changes to the patches!
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Many aligators will be slain, but the swamp will remain.
next prev parent reply other threads:[~2010-08-10 21:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 4:50 [U-Boot] [PATCH 1/9] ARM: Define __raw_readX and __raw_writeX Marek Vasut
2010-08-10 4:50 ` [U-Boot] [PATCH 2/9] PXA: pxafb: Add ACX517AKN support Marek Vasut
2010-08-10 21:45 ` Wolfgang Denk [this message]
2010-08-10 23:56 ` Marek Vasut
2010-08-20 9:31 ` [U-Boot] [PATCH 1/8] " Marek Vasut
2010-08-20 9:31 ` [U-Boot] [PATCH 2/8] common: Enable serial for PXA250 Marek Vasut
2010-08-20 9:31 ` [U-Boot] [PATCH 3/8 v2] PXA: Palm Tungsten|C Support Marek Vasut
2010-08-20 9:31 ` [U-Boot] [PATCH 4/8] PXA: pxafb: Add support for Sharp LQ038J7DH53 Marek Vasut
2010-08-20 9:31 ` [U-Boot] [PATCH 5/8] PXA: Add initial Palm LifeDrive support Marek Vasut
2010-08-20 9:31 ` [U-Boot] [PATCH 6/8] PXA: Voipac270 improvements Marek Vasut
2010-09-07 21:13 ` Wolfgang Denk
2010-09-07 21:30 ` Marek Vasut
2010-09-07 22:34 ` Marek Vasut
2010-08-20 9:31 ` [U-Boot] [PATCH 7/8] PXA: Balloon3 board support Marek Vasut
2010-09-07 21:17 ` Wolfgang Denk
2010-09-07 21:27 ` Marek Vasut
2010-08-20 9:31 ` [U-Boot] [PATCH 8/8] PXA: Add missing MAINTAINERS entries Marek Vasut
2010-08-10 4:50 ` [U-Boot] [PATCH 3/9] common: Enable serial for PXA250 Marek Vasut
2010-08-10 4:50 ` [U-Boot] [PATCH 4/9] PXA: Palm Tungsten|C Support Marek Vasut
2010-08-10 4:50 ` [U-Boot] [PATCH 5/9] PXA: pxafb: Add support for Sharp LQ038J7DH53 Marek Vasut
2010-08-10 4:50 ` [U-Boot] [PATCH 6/9] PXA: Add initial Palm LifeDrive support Marek Vasut
2010-08-10 4:50 ` [U-Boot] [PATCH 7/9] PXA: Voipac270 improvements Marek Vasut
2010-08-10 4:50 ` [U-Boot] [PATCH 8/9] PXA: Balloon3 board support Marek Vasut
2010-08-10 21:52 ` Wolfgang Denk
2010-08-10 4:50 ` [U-Boot] [PATCH 9/9] PXA: Add missing MAINTAINERS entries Marek Vasut
2010-08-10 21:48 ` Wolfgang Denk
2010-08-10 21:38 ` [U-Boot] [PATCH 1/9] ARM: Define __raw_readX and __raw_writeX Wolfgang Denk
2010-08-10 23:52 ` Marek Vasut
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=20100810214505.876721536EF@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/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