From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 3/6] ARM: U8500 core machine support
Date: Mon, 20 Dec 2010 17:08:49 +0000 [thread overview]
Message-ID: <20101220170849.GG28157@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <C832F8F5D375BD43BFA11E82E0FE9FE00829A2FDB7@EXDCVYMBSTM005.EQ1STM.local>
On Mon, Dec 20, 2010 at 05:47:25AM +0100, Srinidhi KASAGAR wrote:
> > -----Original Message-----
> > From: Russell King - ARM Linux [mailto:linux at arm.linux.org.uk]
> > Sent: Sunday, December 19, 2010 4:39 PM
> > To: Srinidhi KASAGAR
> > Cc: linux-arm-kernel at lists.infradead.org; STEricsson_nomadik_linux;
> > Andrea GALLO; rubini at unipv.it
> > Subject: Re: [PATCH v4 3/6] ARM: U8500 core machine support
> >
> > ... going back to this patch...
> >
> > On Fri, Nov 27, 2009 at 05:25:56AM +0530, srinidhi kasagar wrote:
> > > +/*
> > > + * U8500 specific entry point for secondary CPUs.
> > > + */
> > > +ENTRY(u8500_secondary_startup)
> > > + mrc p15, 0, r0, c0, c0, 5
> > > + and r0, r0, #15
> > > + adr r4, 1f
> > > + ldmia r4, {r5, r6}
> > > + sub r4, r4, r5
> > > + add r6, r6, r4
> > > + dsb
> >
> > Can you please explain why you added a dsb here, whereas most other
> > platforms don't require it?
>
> No reason, you can safely ignore this. I can send a patch to remove this
> if you need.
It would be better to have all the pen_release implementations without
spurious differences when the differences aren't necessary.
So, yes please.
prev parent reply other threads:[~2010-12-20 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 23:55 [PATCH v4 3/6] ARM: U8500 core machine support srinidhi kasagar
2010-12-19 11:09 ` Russell King - ARM Linux
2010-12-20 4:47 ` Srinidhi KASAGAR
2010-12-20 17:08 ` Russell King - ARM Linux [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=20101220170849.GG28157@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).