From: Suman Anna <s-anna@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>,
Afzal Mohammed <afzal@ti.com>, Tero Kristo <t-kristo@ti.com>,
Rajendra Nayak <rnayak@ti.com>, Nishant Menon <nm@ti.com>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH] ARM: OMAP2+: hwmod: check for module address space during init
Date: Wed, 9 Oct 2013 12:54:10 -0500 [thread overview]
Message-ID: <52559842.3070400@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1310090529420.30199@utopia.booyaka.com>
Hi Paul,
On 10/09/2013 12:35 AM, Paul Walmsley wrote:
> Hi
>
> On Thu, 3 Oct 2013, Suman Anna wrote:
>
>> The hwmod init sequence involves initializing and idling all the
>> hwmods during bootup. If a module class has sysconfig, the init
>> sequence utilizes the module register base for performing any
>> sysc configuration.
>
> thanks for doing this. A few comments:
>
> 1. The patch adds a warning when checked with 'checkpatch.pl --strict':
>
> CHECK: Alignment should match open parenthesis
> #109: FILE: arch/arm/mach-omap2/omap_hwmod.c:2434:
> + WARN(1, "omap_hwmod: %s: doesn't have mpu register target base\n",
> + oh->name);
>
> The issue has been fixed in in the local copy, but please don't forget to
> ensure that your patches don't generate any warnings[*] from
> 'checkpatch.pl --strict' before sending them.
I have not been using the --strict option, but will change my patch
sanity checking to use it going forward.
>
> [*] Well, with the possible exception of 80-column violations when
> necessary.
>
> 2. -ENOMEM isn't the right error code to use here - it connotates "out of
> memory" rather than "missing address space". -ENXIO seems better, so I've
> changed the patch to use that instead.
OK, thanks for fixing it up.
regards
Suman
next prev parent reply other threads:[~2013-10-09 17:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 16:59 [PATCH] ARM: OMAP2+: hwmod: check for module address space during init Suman Anna
2013-10-03 17:05 ` Santosh Shilimkar
2013-10-07 21:19 ` Nishanth Menon
2013-10-07 22:04 ` Suman Anna
2013-10-08 18:09 ` Tony Lindgren
2013-10-08 21:44 ` Suman Anna
2013-10-09 5:35 ` Paul Walmsley
2013-10-09 17:54 ` Suman Anna [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-11-20 22:14 Paul Walmsley
2013-11-20 22:14 ` Paul Walmsley
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=52559842.3070400@ti.com \
--to=s-anna@ti.com \
--cc=afzal@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=santosh.shilimkar@ti.com \
--cc=t-kristo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.