From: Tony Lindgren <tony@atomide.com>
To: Rajendra Nayak <rnayak@ti.com>
Cc: paul@pwsan.com, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC 0/4] Cleanup PRM and CM regbit headers
Date: Thu, 4 Jul 2013 04:58:19 -0700 [thread overview]
Message-ID: <20130704115819.GJ5523@atomide.com> (raw)
In-Reply-To: <51C95839.6050307@ti.com>
* Rajendra Nayak <rnayak@ti.com> [130625 01:49]:
> On Tuesday 25 June 2013 12:44 PM, Tony Lindgren wrote:
> >> Rajendra Nayak (4):
> >> > ARM: OMAP2: PRM/CM: Cleanup unused header contents
> >> > ARM: OMAP3: PRM/CM: Cleanup unused header contents
> >> > ARM: OMAP4: PRM/CM: Cleanup unused header contents
> >> > ARM: OMAP5: PRM/CM: Cleanup unused header contents
> >> >
> >> > arch/arm/mach-omap2/cm-regbits-24xx.h | 317 ----
> >> > arch/arm/mach-omap2/cm-regbits-33xx.h | 758 ---------
> >> > arch/arm/mach-omap2/cm-regbits-34xx.h | 631 --------
> >> > arch/arm/mach-omap2/cm-regbits-44xx.h | 1557 -------------------
> >> > arch/arm/mach-omap2/cm-regbits-54xx.h | 1632 -------------------
> >> > arch/arm/mach-omap2/prm-regbits-24xx.h | 246 ---
> >> > arch/arm/mach-omap2/prm-regbits-33xx.h | 305 ----
> >> > arch/arm/mach-omap2/prm-regbits-34xx.h | 480 ------
> >> > arch/arm/mach-omap2/prm-regbits-44xx.h | 2225 --------------------------
> >> > arch/arm/mach-omap2/prm-regbits-54xx.h | 2677 --------------------------------
> >> > 10 files changed, 10828 deletions(-)
> > If things build and work after applying this, I suggest we send them
> > as a clean-up branch right after -rc1.
>
> They build fine, and I boot tested on the omap4/5 boards that I have too.
> (I had the out of tree clock data pulled in for omap5 before I did this
> cleanup).
>
> >
> > It seems that build testing and then randconfig testing
> > should be enough for these if they are unused and only
> > removal.
>
> Right, I'll do more testing and even though they should just boot
> fine on the omap2/3 boards too since all thats removed is anyway
> unused, I will still do more sanity test before posting them on -rc1.
Looks like we have all the pending stuff merged already, this would
probably be a good time to post a pull request for these.
Tony
next prev parent reply other threads:[~2013-07-04 11:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 12:15 [RFC 0/4] Cleanup PRM and CM regbit headers Rajendra Nayak
2013-06-24 12:15 ` [RFC 1/4] ARM: OMAP2: PRM/CM: Cleanup unused header contents Rajendra Nayak
2013-06-24 12:15 ` [RFC 2/4] ARM: OMAP3: " Rajendra Nayak
2013-06-25 7:14 ` [RFC 0/4] Cleanup PRM and CM regbit headers Tony Lindgren
2013-06-25 8:43 ` Rajendra Nayak
2013-07-04 11:58 ` Tony Lindgren [this message]
2013-07-04 12:14 ` Rajendra Nayak
2013-07-04 16:44 ` Paul Walmsley
2013-07-05 5:43 ` Rajendra Nayak
2013-07-05 7:03 ` Tony Lindgren
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=20130704115819.GJ5523@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rnayak@ti.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).