From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: "Manjunathappa, Prakash" <prakash.pm@ti.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
Sekhar Nori <nsekhar@ti.com>,
davinci-linux-open-source@linux.davincidsp.com,
David Woodhouse <dwmw2@infradead.org>,
Samuel Ortiz <sameo@linux.intel.com>
Subject: Re: [RESEND PATCH] arm:davinci: prepare to move aemif driver to drivers/mfd
Date: Mon, 23 Jan 2012 17:04:36 +0000 [thread overview]
Message-ID: <20120123170436.GZ1068@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1327331552-9913-1-git-send-email-prakash.pm@ti.com>
On Mon, Jan 23, 2012 at 08:42:32PM +0530, Manjunathappa, Prakash wrote:
> Adding: MFD maintainer and mailing list.
>
> arch/arm/mach-davinci/aemif.c | 2 +-
> arch/arm/mach-davinci/board-da830-evm.c | 2 +-
> arch/arm/mach-davinci/board-da850-evm.c | 2 +-
> arch/arm/mach-davinci/include/mach/aemif.h | 36 ----------------------------
> drivers/mtd/nand/davinci_nand.c | 2 +-
> include/linux/mfd/davinci_aemif.h | 36 ++++++++++++++++++++++++++++
> 6 files changed, 40 insertions(+), 40 deletions(-)
> delete mode 100644 arch/arm/mach-davinci/include/mach/aemif.h
> create mode 100644 include/linux/mfd/davinci_aemif.h
As Linus has requested on many occasions, and it's a damned good
idea, use -M when generating diffstat - and its also a *really* good
idea to use -M if you're submitting patches which rename files for
review as well.
Obviously arch/arm/mach-davinci/include/mach/aemif.h was moved to
include/linux/mfd/davinci_aemif.h, but were there any changes to its
contents? Without -M, there only way of knowing is to compare each
file line by line. With -M, it'll tell us that it was renamed and
produce a diff between the old and new location.
next prev parent reply other threads:[~2012-01-23 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 15:12 Manjunathappa, Prakash
2012-01-23 17:04 ` Russell King - ARM Linux [this message]
2012-01-24 5:24 ` Manjunathappa, Prakash
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=20120123170436.GZ1068@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=dwmw2@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nsekhar@ti.com \
--cc=prakash.pm@ti.com \
--cc=sameo@linux.intel.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
all inboxes | Powered by JetHome®