From: jacmet@sunsite.dk (Peter Korsgaard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/9] ARM: OMAP2+: AM33XX: Misc fixes/updates
Date: Mon, 21 Jan 2013 10:03:20 +0100 [thread overview]
Message-ID: <87zk02aox3.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <B5906170F1614E41A8A28DE3B8D121433ECF09E0@DBDE01.ent.ti.com> (Vaibhav Bedia's message of "Mon, 21 Jan 2013 05:27:16 +0000")
>>>>> "V" == Bedia, Vaibhav <vaibhav.bedia@ti.com> writes:
Hi,
>> Vaibhav Bedia (9):
>> ARM: OMAP2+: AM33XX: CM: Get rid of unncessary header inclusions
>> ARM: OMAP2+: AM33XX: CM/PRM: Use __ASSEMBLER__ macros in header files
>> ARM: OMAP2+: AM33XX: hwmod: Register OCMC RAM hwmod
>> ARM: OMAP2+: AM33XX: hwmod: Update TPTC0 hwmod with the right flags
>> ARM: OMAP2+: AM33XX: hwmod: Fixup cpgmac0 hwmod entry
>> ARM: OMAP2+: AM33XX: hwmod: Update the WKUP-M3 hwmod with reset
>> status bit
>> ARM: OMAP2+: AM33XX: Update the hardreset API
>> ARM: DTS: AM33XX: Add nodes for OCMC RAM and WKUP-M3
>> ARM: OMAP2+: AM33XX: control: Add some control module registers and
>> APIs
>>
V> Any comments on these before I resend addressing the comments from Sergei?
Wouldn't the ocmram/wkup dt nodes need a reg property to define their
size as I indirectly mentioned here:
http://thread.gmane.org/gmane.linux.ports.arm.omap/91405/focus=92061
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-01-21 9:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 7:19 [PATCH 0/9] ARM: OMAP2+: AM33XX: Misc fixes/updates Vaibhav Bedia
2013-01-18 7:19 ` [PATCH 1/9] ARM: OMAP2+: AM33XX: CM: Get rid of unncessary header inclusions Vaibhav Bedia
2013-01-18 12:31 ` Sergei Shtylyov
2013-01-21 5:27 ` Bedia, Vaibhav
2013-01-18 7:19 ` [PATCH 2/9] ARM: OMAP2+: AM33XX: CM/PRM: Use __ASSEMBLER__ macros in header files Vaibhav Bedia
2013-01-18 7:19 ` [PATCH 3/9] ARM: OMAP2+: AM33XX: hwmod: Register OCMC RAM hwmod Vaibhav Bedia
2013-01-18 7:19 ` [PATCH 4/9] ARM: OMAP2+: AM33XX: hwmod: Update TPTC0 hwmod with the right flags Vaibhav Bedia
2013-01-18 12:28 ` Sergei Shtylyov
2013-01-21 5:27 ` Bedia, Vaibhav
2013-01-18 7:19 ` [PATCH 5/9] ARM: OMAP2+: AM33XX: hwmod: Fixup cpgmac0 hwmod entry Vaibhav Bedia
2013-01-18 7:19 ` [PATCH 6/9] ARM: OMAP2+: AM33XX: hwmod: Update the WKUP-M3 hwmod with reset status bit Vaibhav Bedia
2013-01-18 7:19 ` [PATCH 7/9] ARM: OMAP2+: AM33XX: Update the hardreset API Vaibhav Bedia
2013-01-18 7:19 ` [PATCH 8/9] ARM: DTS: AM33XX: Add nodes for OCMC RAM and WKUP-M3 Vaibhav Bedia
2013-01-18 7:19 ` [PATCH 9/9] ARM: OMAP2+: AM33XX: control: Add some control module registers and APIs Vaibhav Bedia
2013-01-21 5:27 ` [PATCH 0/9] ARM: OMAP2+: AM33XX: Misc fixes/updates Bedia, Vaibhav
2013-01-21 9:03 ` Peter Korsgaard [this message]
2013-01-21 10:37 ` Bedia, Vaibhav
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=87zk02aox3.fsf@dell.be.48ers.dk \
--to=jacmet@sunsite.dk \
--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