From: David Brown <davidb@codeaurora.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Russell King <linux@arm.linux.org.uk>,
Daniel Walker <dwalker@fifo99.com>,
Bryan Huntsman <bryanh@codeaurora.org>,
Chris Ball <cjb@laptop.org>,
Florian Tobias Schandinat <FlorianSchandinat@gmx.de>,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 05/16] ARM: msm: move platform_data definitions
Date: Tue, 11 Sep 2012 14:07:26 -0700 [thread overview]
Message-ID: <20120911210726.GA17002@codeaurora.org> (raw)
In-Reply-To: <1347368390-31252-5-git-send-email-arnd@arndb.de>
On Tue, Sep 11, 2012 at 02:59:39PM +0200, Arnd Bergmann wrote:
> Platform data for device drivers should be defined in
> include/linux/platform_data/*.h, not in the architecture
> and platform specific directories.
>
> This moves such data out of the msm include directories
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Cc: David Brown <davidb@codeaurora.org>
> Cc: Daniel Walker <dwalker@fifo99.com>
> Cc: Bryan Huntsman <bryanh@codeaurora.org>
> Cc: Chris Ball <cjb@laptop.org>
> Cc: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
> Cc: linux-arm-msm@vger.kernel.org
> ---
> arch/arm/mach-msm/board-qsd8x50.c | 2 +-
> arch/arm/mach-msm/board-trout-mmc.c | 2 +-
> arch/arm/mach-msm/board-trout-panel.c | 2 +-
> arch/arm/mach-msm/devices-msm7x00.c | 2 +-
> arch/arm/mach-msm/devices-msm7x30.c | 2 +-
> arch/arm/mach-msm/devices-qsd8x50.c | 2 +-
> arch/arm/mach-msm/include/mach/board.h | 2 +-
> drivers/mmc/host/msm_sdcc.c | 2 +-
> drivers/video/msm/mddi.c | 2 +-
> drivers/video/msm/mddi_client_dummy.c | 2 +-
> drivers/video/msm/mddi_client_nt35399.c | 2 +-
> drivers/video/msm/mddi_client_toshiba.c | 2 +-
> drivers/video/msm/mdp.c | 2 +-
> drivers/video/msm/mdp_hw.h | 2 +-
> drivers/video/msm/mdp_ppp.c | 2 +-
> drivers/video/msm/msm_fb.c | 2 +-
> .../include/mach/mmc.h => include/linux/platform_data/mmc-msm_sdcc.h | 0
> .../mach/msm_fb.h => include/linux/platform_data/video-msm_fb.h | 0
> 18 files changed, 16 insertions(+), 16 deletions(-)
> rename arch/arm/mach-msm/include/mach/mmc.h => include/linux/platform_data/mmc-msm_sdcc.h (100%)
> rename arch/arm/mach-msm/include/mach/msm_fb.h => include/linux/platform_data/video-msm_fb.h (100%)
Acked-by: David Brown <davidb@codeaurora.org>
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
prev parent reply other threads:[~2012-09-11 21:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1347368245-30989-1-git-send-email-arnd@arndb.de>
2012-09-11 12:59 ` [PATCH 00/16] ARM: big platform data header rename Arnd Bergmann
[not found] ` <1347368390-31252-1-git-send-email-arnd@arndb.de>
2012-09-11 12:59 ` [PATCH 05/16] ARM: msm: move platform_data definitions Arnd Bergmann
2012-09-11 21:07 ` David Brown [this message]
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=20120911210726.GA17002@codeaurora.org \
--to=davidb@codeaurora.org \
--cc=FlorianSchandinat@gmx.de \
--cc=arnd@arndb.de \
--cc=bryanh@codeaurora.org \
--cc=cjb@laptop.org \
--cc=dwalker@fifo99.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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).