From: Eric Miao <eric.y.miao@gmail.com>
To: Jaya Kumar <jayakumar.lkml@gmail.com>
Cc: ymiao3@marvell.com, linux-fbdev-devel@lists.sourceforge.net,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [RFC 2.6.26-rc3 07/10] am200epd: move am200epd to mach-pxa
Date: Mon, 16 Jun 2008 10:29:23 +0800 [thread overview]
Message-ID: <4855D003.1040306@gmail.com> (raw)
In-Reply-To: <45a44e480806142323h438e82a6ye4e57e83ce872e1b@mail.gmail.com>
Jaya Kumar wrote:
> On Thu, Jun 12, 2008 at 10:12 PM, Eric Miao <eric.y.miao@gmail.com> wrote:
>> Jaya Kumar wrote:
>>> The am200epd driver was designed with bad assumptions. It manipulated
>>> GPSR/GPLR registers directly. It relied on direct access to the pxa LCDC
>>> registers which have since conflicted with commit
>>> ce4fb7b892a6d6c6a0f87366b26fd834d2923dd7 . This patch moves it into
>>> mach-pxa in preparation for an overhaul. This is done as a move rather
>>> than a removal in order to facilitate code review.
>> You may generate the patch with "-M" option, so that git can recognize
>> the file rename/move change.
>
> Thanks! I had used git-mv and wondered why the patch was just a normal
> diff when I generated it. For any other git newbies like myself, it
> was:
>
> git-format-patch -M -n --signoff --subject-prefix="RFC 2.6.26-rc3"
> eb90d81d03c0917b0fd629f6342554a3b58ea52c
> and that gives a nice:
> ---
> arch/arm/mach-pxa/Kconfig | 17 +++++++++++++++++
> arch/arm/mach-pxa/Makefile | 1 +
> {drivers/video => arch/arm/mach-pxa}/am200epd.c | 0
> drivers/video/Kconfig | 13 -------------
> drivers/video/Makefile | 1 -
> 5 files changed, 18 insertions(+), 14 deletions(-)
> rename {drivers/video => arch/arm/mach-pxa}/am200epd.c (100%)
>
>> Also, I think it would be better to merge this commit with your
>> following [patch 08] am200epd: conver to share fb and use gpio api,
>> that will be helpful for code review, and "-M" option should be
>> smart enough to make the change clear.
>>
>
> Ok, git doesn't give me that result. When I merged the move patch with
> the change patch, it no longer detects it as a move. I get the
> following output:
>
> arch/arm/mach-pxa/Kconfig | 17 ++
> arch/arm/mach-pxa/Makefile | 1 +
> arch/arm/mach-pxa/am200epd.c | 347 ++++++++++++++++++++++++++++++++++++++++++
> arch/arm/mach-pxa/devices.c | 1 +
> drivers/video/Kconfig | 13 --
> drivers/video/Makefile | 1 -
> drivers/video/am200epd.c | 295 -----------------------------------
> 7 files changed, 366 insertions(+), 309 deletions(-)
> create mode 100644 arch/arm/mach-pxa/am200epd.c
> delete mode 100644 drivers/video/am200epd.c
>
> If it's okay, then I'll just use that when I regenerate the patchset next time.
>
Either way is fine to me.
> Thanks,
> jaya
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
next prev parent reply other threads:[~2008-06-16 2:29 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 16:59 [RFC 2.6.26-rc3 0/10] am200epd, pxafb, metronomefb changes v4 Jaya Kumar
2008-06-12 16:59 ` [RFC 2.6.26-rc3 01/10] pxafb: fix ifdef for command line option handling Jaya Kumar
[not found] ` <20080612203541.0baa5586.krzysztof.h1@poczta.fm>
2008-06-13 1:22 ` Eric Miao
2008-06-13 7:37 ` Russell King - ARM Linux
2008-06-12 16:59 ` [RFC 2.6.26-rc3 02/10] pxafb: cleanup and fix order of failure handling Jaya Kumar
2008-06-12 18:36 ` Krzysztof Helt
2008-06-13 1:23 ` Eric Miao
2008-06-13 7:37 ` Russell King - ARM Linux
2008-06-12 16:59 ` [RFC 2.6.26-rc3 03/10] pxafb: fix __devinit/exit annotations Jaya Kumar
2008-06-12 18:36 ` [Linux-fbdev-devel] " Krzysztof Helt
2008-06-13 1:24 ` Eric Miao
2008-06-13 7:38 ` Russell King - ARM Linux
2008-06-12 16:59 ` [RFC 2.6.26-rc3 04/10] pxafb: add exit and remove handlers Jaya Kumar
2008-06-12 18:37 ` [Linux-fbdev-devel] " Krzysztof Helt
2008-06-13 1:24 ` Eric Miao
2008-06-13 7:39 ` Russell King - ARM Linux
2008-06-12 16:59 ` [RFC 2.6.26-rc3 05/10] pxafb: add shared framebuffer interface Jaya Kumar
2008-06-15 6:26 ` [Linux-fbdev-devel] " Krzysztof Helt
2008-06-15 6:49 ` Jaya Kumar
2008-06-12 16:59 ` [RFC 2.6.26-rc3 06/10] gumstix: conversion to MFP support and add bluetooth support Jaya Kumar
2008-06-13 2:01 ` Eric Miao
2008-06-15 5:51 ` Jaya Kumar
2008-06-16 2:21 ` Eric Miao
2008-07-04 5:01 ` Jaya Kumar
2008-07-08 0:52 ` Jaya Kumar
2008-06-13 7:42 ` Russell King - ARM Linux
2008-06-15 5:54 ` Jaya Kumar
2008-07-31 9:04 ` Andrew Morton
2008-06-12 16:59 ` [RFC 2.6.26-rc3 07/10] am200epd: move am200epd to mach-pxa Jaya Kumar
2008-06-13 2:12 ` Eric Miao
2008-06-15 6:23 ` Jaya Kumar
2008-06-16 2:29 ` Eric Miao [this message]
2008-06-12 16:59 ` [RFC 2.6.26-rc3 08/10] am200epd: convert to shared fb and use gpio api Jaya Kumar
2008-06-13 2:20 ` Eric Miao
2008-06-15 6:42 ` Jaya Kumar
2008-06-16 2:35 ` Eric Miao
2008-07-08 12:43 ` Jaya Kumar
2008-06-12 16:59 ` [RFC 2.6.26-rc3 09/10] metronomefb: convert printk to dev_dbg/err messages Jaya Kumar
2008-06-13 2:22 ` Eric Miao
2008-06-12 16:59 ` [RFC 2.6.26-rc3 10/10] metronomefb: changes to use separate framebuffer Jaya Kumar
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=4855D003.1040306@gmail.com \
--to=eric.y.miao@gmail.com \
--cc=jayakumar.lkml@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=ymiao3@marvell.com \
/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).