From: srinidhikasagar@gmail.com (Srinidhi Kasagar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Common GIC entry macro code
Date: Wed, 10 Nov 2010 13:17:43 +0530 [thread overview]
Message-ID: <AANLkTimjCB265Nv+wHZ8C2s+s--gi5Azgu1-uQNiDbAi@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikOkqzagFRTQRysEKw1JhZ9a1tMm1fMOoiMC9q4@mail.gmail.com>
On Wed, Nov 10, 2010 at 1:05 PM, Magnus Damm <magnus.damm@gmail.com> wrote:
> On Wed, Nov 10, 2010 at 4:16 PM, Shilimkar, Santosh
> <santosh.shilimkar@ti.com> wrote:
>>> Subject: [PATCH] ARM: Common GIC entry macro code
>>>
>> I guess this was attempted by below patch as well.
>> http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=6284%2F1
>>
>> 6284/1 in the RMKs patch system. This was also addressing OMAP and the
>> patch was tested OK.
>
> Thanks for the pointer! Looks almost identical to what I just hacked
> up. The main difference seems to be that the implementation in the
> tracker depends on "gic_cpu_base_addr" which isn't used by all
> sub-architectures.
>
>> Looks like it needs to be rebased because the state I see in the patch
>> System is
>>
>> - - Note 2 submitted by Russell King on 02 Sep 2010 15:43:12 (UTC) - - -
>> Moved to Discarded.
>>
>> Doesn't apply:
>
> Ironically enough it looks like it was the omap2 bits that didn't
> apply properly.
>
> If I don't hear anything then I'll just resend my patch to the
> tracker. If the other implementation gets merged sooner then that's
> even better - having some code to share is much better than
> duplicating the same code again and again.
If you rebase to the discarded one in tracker, I would be happy.
Anyway Acked-by: Srinidhi Kasagar<srinidhi.kasagar@stericsson.com>
Srinidhi
next prev parent reply other threads:[~2010-11-10 7:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 7:00 [PATCH] ARM: Common GIC entry macro code Magnus Damm
2010-11-10 7:16 ` Shilimkar, Santosh
2010-11-10 7:35 ` Magnus Damm
2010-11-10 7:47 ` Srinidhi Kasagar [this message]
2010-11-10 20:28 ` Abhijeet Dharmapurikar
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=AANLkTimjCB265Nv+wHZ8C2s+s--gi5Azgu1-uQNiDbAi@mail.gmail.com \
--to=srinidhikasagar@gmail.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).