From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Yuriy Kolerov <yuriy.kolerov@synopsys.com>,
<linux-snps-arc@lists.infradead.org>
Cc: <marc.zyngier@arm.com>, <Alexey.Brodkin@synopsys.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/4] ARCv2: IRQ: Move structure for build register of core intc to the header
Date: Tue, 31 Jan 2017 09:40:14 -0800 [thread overview]
Message-ID: <731065b1-3fde-02f0-a18b-690c84af2dcc@synopsys.com> (raw)
In-Reply-To: <1485863124-26426-2-git-send-email-yuriy.kolerov@synopsys.com>
On 01/31/2017 03:45 AM, Yuriy Kolerov wrote:
> Also add new macro ARC_REG_STATUS32 for the address of STATUS32
> auxiliary register. It is better to use it instead of magic numbers.
>
> Signed-off-by: Yuriy Kolerov <yuriy.kolerov@synopsys.com>
Applied to for-next.
Thx,
-Vineet
next prev parent reply other threads:[~2017-01-31 17:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 11:45 [PATCH v2 0/4] Use build registers for getting numbers of interrupts Yuriy Kolerov
2017-01-31 11:45 ` [PATCH v2 1/4] ARCv2: IRQ: Move structure for build register of core intc to the header Yuriy Kolerov
2017-01-31 17:40 ` Vineet Gupta [this message]
2017-01-31 18:15 ` Vineet Gupta
2017-01-31 11:45 ` [PATCH v2 2/4] ARCv2: IRQ: Remove option for setting number of interrupts Yuriy Kolerov
2017-01-31 17:40 ` Vineet Gupta
2017-01-31 11:45 ` [PATCH v2 3/4] ARCv2: IRQ: Use build registers for getting numbers " Yuriy Kolerov
2017-01-31 17:46 ` Vineet Gupta
2017-01-31 11:45 ` [PATCH v2 4/4] ARCv2: IRQ: Set a default priority for all core interrupts Yuriy Kolerov
2017-01-31 17:54 ` Vineet Gupta
2017-02-01 12:54 ` Yuriy Kolerov
2017-02-01 20:58 ` [PATCH v2 0/4] Use build registers for getting numbers of interrupts Vineet Gupta
2017-02-01 23:59 ` Yuriy Kolerov
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=731065b1-3fde-02f0-a18b-690c84af2dcc@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=yuriy.kolerov@synopsys.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®