From: Andrii Anisov <andrii.anisov@gmail.com>
To: Julien Grall <julien.grall@arm.com>, xen-devel@lists.xenproject.org
Cc: andre.przywara@arm.com, sstabellini@kernel.org
Subject: Re: [PATCH for-next] xen/arm: irq: Don't use _IRQ_PENDING when handling host interrupt
Date: Fri, 5 Apr 2019 17:59:53 +0300 [thread overview]
Message-ID: <294d08cf-de0b-35cd-42a4-1571f7ae53b4@gmail.com> (raw)
In-Reply-To: <8dec40f1-3b28-d178-13e9-f0dbcde8b7c2@arm.com>
Hello Julien,
On 05.04.19 17:34, Julien Grall wrote:
> It is in common header and used by x86. It is preferable to keep all IRQ flags at the same place hence why this was not moved in arch-specific header.
Ah, yes, sure.
Reviewed-by: Andrii Anisov <andrii_anisov@epam.com>
--
Sincerely,
Andrii Anisov.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: Andrii Anisov <andrii.anisov@gmail.com>
To: Julien Grall <julien.grall@arm.com>, xen-devel@lists.xenproject.org
Cc: andre.przywara@arm.com, sstabellini@kernel.org
Subject: Re: [Xen-devel] [PATCH for-next] xen/arm: irq: Don't use _IRQ_PENDING when handling host interrupt
Date: Fri, 5 Apr 2019 17:59:53 +0300 [thread overview]
Message-ID: <294d08cf-de0b-35cd-42a4-1571f7ae53b4@gmail.com> (raw)
Message-ID: <20190405145953.16W1w1GZpy1XhAnXJf1pV_BfyvqAzPTpPJ0FLzVig88@z> (raw)
In-Reply-To: <8dec40f1-3b28-d178-13e9-f0dbcde8b7c2@arm.com>
Hello Julien,
On 05.04.19 17:34, Julien Grall wrote:
> It is in common header and used by x86. It is preferable to keep all IRQ flags at the same place hence why this was not moved in arch-specific header.
Ah, yes, sure.
Reviewed-by: Andrii Anisov <andrii_anisov@epam.com>
--
Sincerely,
Andrii Anisov.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-04-05 14:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 15:59 [PATCH for-next] xen/arm: irq: Don't use _IRQ_PENDING when handling host interrupt Julien Grall
2019-03-19 23:28 ` Julien Grall
2019-04-05 14:16 ` Andrii Anisov
2019-04-05 14:16 ` [Xen-devel] " Andrii Anisov
2019-04-05 14:34 ` Julien Grall
2019-04-05 14:34 ` [Xen-devel] " Julien Grall
2019-04-05 14:59 ` Andrii Anisov [this message]
2019-04-05 14:59 ` Andrii Anisov
2019-04-16 21:51 ` Stefano Stabellini
2019-04-16 21:51 ` [Xen-devel] " Stefano Stabellini
2019-04-16 22:07 ` Julien Grall
2019-04-16 22:07 ` [Xen-devel] " Julien Grall
2019-04-17 17:12 ` Stefano Stabellini
2019-04-17 17:12 ` [Xen-devel] " Stefano Stabellini
2019-04-17 17:24 ` Julien Grall
2019-04-17 17:24 ` [Xen-devel] " Julien Grall
2019-04-17 17:27 ` Stefano Stabellini
2019-04-17 17:27 ` [Xen-devel] " Stefano Stabellini
2019-05-20 15:15 ` Julien Grall
2019-05-20 15:15 ` [Xen-devel] " Julien Grall
2019-05-20 21:04 ` Stefano Stabellini
2019-05-20 21:04 ` [Xen-devel] " Stefano Stabellini
2019-05-21 10:11 ` Julien Grall
2019-05-21 10:11 ` [Xen-devel] " Julien Grall
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=294d08cf-de0b-35cd-42a4-1571f7ae53b4@gmail.com \
--to=andrii.anisov@gmail.com \
--cc=andre.przywara@arm.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).