From: Kevin Hilman <khilman@deeprootsystems.com>
To: Hari Kanigeri <h-kanigeri2@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>, Linux Omap <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] omap:hwmod-remove prm header from prm-regbits-xxxx headers
Date: Thu, 20 May 2010 10:12:33 -0700 [thread overview]
Message-ID: <87bpcafqf2.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1274307029-22032-1-git-send-email-h-kanigeri2@ti.com> (Hari Kanigeri's message of "Wed\, 19 May 2010 17\:10\:29 -0500")
Hari Kanigeri <h-kanigeri2@ti.com> writes:
> The prm-regbits-xxxx.h header files are not dependent on prm.h
> header file.
>
> Signed-off-by: Hari Kanigeri <h-kanigeri2@ti.com>
> ---
> arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 1 +
This file is not in mailine, or linux-omap master. Please
state any dependencies in this part of the changelog.
Kevin
> arch/arm/mach-omap2/prm-regbits-24xx.h | 1 -
> arch/arm/mach-omap2/prm-regbits-34xx.h | 1 -
> arch/arm/mach-omap2/prm-regbits-44xx.h | 1 -
> 4 files changed, 1 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> index 667633c..88cc9ca 100644
> --- a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> +++ b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> @@ -26,6 +26,7 @@
> #include "omap_hwmod_common_data.h"
>
> #include "cm.h"
> +#include "prm.h"
> #include "prm-regbits-44xx.h"
>
> /* Base offset for all OMAP4 interrupts external to MPUSS */
> diff --git a/arch/arm/mach-omap2/prm-regbits-24xx.h b/arch/arm/mach-omap2/prm-regbits-24xx.h
> index 4002051..fd763b5 100644
> --- a/arch/arm/mach-omap2/prm-regbits-24xx.h
> +++ b/arch/arm/mach-omap2/prm-regbits-24xx.h
> @@ -14,7 +14,6 @@
> * published by the Free Software Foundation.
> */
>
> -#include "prm.h"
>
> /* Bits shared between registers */
>
> diff --git a/arch/arm/mach-omap2/prm-regbits-34xx.h b/arch/arm/mach-omap2/prm-regbits-34xx.h
> index 8f21bae..ef7fd5e 100644
> --- a/arch/arm/mach-omap2/prm-regbits-34xx.h
> +++ b/arch/arm/mach-omap2/prm-regbits-34xx.h
> @@ -14,7 +14,6 @@
> * published by the Free Software Foundation.
> */
>
> -#include "prm.h"
>
> /* Shared register bits */
>
> diff --git a/arch/arm/mach-omap2/prm-regbits-44xx.h b/arch/arm/mach-omap2/prm-regbits-44xx.h
> index 597be4a..ef7af7e 100644
> --- a/arch/arm/mach-omap2/prm-regbits-44xx.h
> +++ b/arch/arm/mach-omap2/prm-regbits-44xx.h
> @@ -22,7 +22,6 @@
> #ifndef __ARCH_ARM_MACH_OMAP2_PRM_REGBITS_44XX_H
> #define __ARCH_ARM_MACH_OMAP2_PRM_REGBITS_44XX_H
>
> -#include "prm.h"
>
>
> /*
> --
> 1.7.0
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-05-20 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 22:10 [PATCH] omap:hwmod-remove prm header from prm-regbits-xxxx headers Hari Kanigeri
2010-05-20 17:12 ` Kevin Hilman [this message]
2010-05-20 18:25 ` Kanigeri, Hari
2010-05-20 21:30 ` Benoit Cousson
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=87bpcafqf2.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=h-kanigeri2@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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).