From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: OMAP4+: PM: centralize static dependency mapping table
Date: Mon, 10 Nov 2014 16:02:44 -0800 [thread overview]
Message-ID: <20141111000243.GI31454@atomide.com> (raw)
In-Reply-To: <1413922949-22300-1-git-send-email-nm@ti.com>
* Nishanth Menon <nm@ti.com> [141021 13:23]:
> Hi,
>
> This is a small step towards getting rid of static dependency logic
> from mach-omap2. As part of this, we split the list of static dep
> map from the function implementing it. This should eventually aid in
> helping remove the tables from the kernel to the device tree at a
> later point in time of cleanup.
>
> Series based on v3.18-rc1 and could be a 3.19-rc1 material.
Applying into omap-for-3.19/soc thanks.
Tony
prev parent reply other threads:[~2014-11-11 0:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 20:22 [PATCH 0/2] ARM: OMAP4+: PM: centralize static dependency mapping table Nishanth Menon
2014-10-21 20:22 ` [PATCH 1/2] ARM: OMAP4: PM: Only do static dependency configuration in omap4_init_static_deps Nishanth Menon
2014-10-21 20:22 ` [PATCH 2/2] ARM: OMAP4+: PM: Centralize static dependency mapping table Nishanth Menon
2014-11-11 0:02 ` Tony Lindgren [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=20141111000243.GI31454@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).