public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Dongjin Kim <Dongjin.Kim@agreeyamobility.net>
Cc: Dongjin Kim <tobetter@gmail.com>,
	Russell King <linux@arm.linux.org.uk>,
	Thomas Abraham <thomas.abraham@linaro.org>,
	Kukjin Kim <kgene.kim@samsung.com>,
	Grant Likely <grant.likely@secretlab.ca>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re:  회신: [PATCH 2/4] arm/dts: exynos4: Add DTS files derived from common Exynos4
Date: Tue, 7 Aug 2012 20:29:08 +0000	[thread overview]
Message-ID: <201208072029.08693.arnd@arndb.de> (raw)
In-Reply-To: <A6A3B7488C419F488E5B13FFD03C08AD2F4372EB@SN2PRD0510MB370.namprd05.prod.outlook.com>

On Tuesday 07 August 2012, Dongjin Kim wrote:
> Hi,
> 
> I didn't use -M and I couldn't see any difference with the it.
> Did I make something wrong on that patch?

No, I think it's just git being less smart about file moves than I was hoping
for. It might do the right thing if you do the patch in two steps:

1. rename exynos4210.dtsi to exynos4.dtsi and add a one-line exynos4210.dtsi
file that just includes exynos4.dtsi.

2. do all the changes for moving contents back from exynos4.dtsi into
exynos4210.dtsi and exynos4412.dtsi.

Not sure if it's worth it though. Your version is probably good enough
if there are no tools to do a better job automatically.

	Arnd

  reply	other threads:[~2012-08-07 20:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-07 19:06 [PATCH 2/4] arm/dts: exynos4: Add DTS files derived from common Exynos4 Dongjin Kim
2012-08-07 19:38 ` Arnd Bergmann
2012-08-07 19:57   ` 회신: " Dongjin Kim
2012-08-07 20:29     ` Arnd Bergmann [this message]
2012-08-08  2:08       ` Kukjin Kim
2012-08-08  3:38 ` Thomas Abraham

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=201208072029.08693.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=Dongjin.Kim@agreeyamobility.net \
    --cc=grant.likely@secretlab.ca \
    --cc=kgene.kim@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=thomas.abraham@linaro.org \
    --cc=tobetter@gmail.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