From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Todd Poynor <toddpoynor@google.com>
Cc: Tony Lindgren <tony@atomide.com>, linux-omap@vger.kernel.org
Subject: Re: [PATCH] ARM: OMAP: L3 interconnect: Error reporting cleanups
Date: Wed, 25 May 2011 12:39:56 +0530 [thread overview]
Message-ID: <4DDCAB44.2060006@ti.com> (raw)
In-Reply-To: <20110525025021.GA8460@google.com>
Tod,
On 5/25/2011 8:20 AM, Todd Poynor wrote:
> * Move variable declarations from header file and make these static
> (the entire header file should probably go away).
>
Infact the intial version posted on the list had all these structures
in C file. After some comments on the list we moved them to header file.
Let's not move it again.
> * Define L3 TARG instance offsets, and read/write STDERRLOG registers
> relative to those offsets, rather than defining STDERRLOG_MAIN
> instance offsets and accessing other registers via offsets from
> that register.
>
> * Use ffs() to find error source from the L3_FLAGMUX_REGERRn
> register.
>
> * Remove extra l3_base[] entry.
>
> * Modify L3 custom error message for consistency with standard
> error message.
>
These changes are ok.
> * Fixup indentation in one spot.
>
This code indentations needs more fixing and I have patch to
clean that up. Your change is already part of that patch.
> ---
> arch/arm/mach-omap2/omap_l3_noc.c | 122 +++++++++++++++++++++++++++++++------
> arch/arm/mach-omap2/omap_l3_noc.h | 88 +-------------------------
> 2 files changed, 106 insertions(+), 104 deletions(-)
>
Can you update your patch with above. I will add that along with other
L3 clean-up patch.
Thanks
regards
Santosh
next prev parent reply other threads:[~2011-05-25 7:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 2:50 [PATCH] ARM: OMAP: L3 interconnect: Error reporting cleanups Todd Poynor
2011-05-25 7:09 ` Santosh Shilimkar [this message]
2011-05-25 18:43 ` Todd Poynor
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=4DDCAB44.2060006@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=toddpoynor@google.com \
--cc=tony@atomide.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.