From: Catalin Marinas <catalin.marinas@arm.com>
To: Will Deacon <will@kernel.org>
Cc: xen-devel@lists.xenproject.org, Mark Brown <broonie@kernel.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien@xen.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] arm64: xen: Use modern annotations for assembly functions
Date: Thu, 9 Jan 2020 15:58:24 +0000 [thread overview]
Message-ID: <20200109155824.GG25655@arrakis.emea.arm.com> (raw)
In-Reply-To: <20200108155551.GA19197@willie-the-truck>
On Wed, Jan 08, 2020 at 03:55:52PM +0000, Will Deacon wrote:
> On Thu, Dec 19, 2019 at 01:07:50PM -0800, Stefano Stabellini wrote:
> > On Thu, 19 Dec 2019, Mark Brown wrote:
> > > In an effort to clarify and simplify the annotation of assembly functions
> > > in the kernel new macros have been introduced. These replace ENTRY and
> > > ENDPROC. Update the annotations in the xen code to the new macros.
> > >
> > > Signed-off-by: Mark Brown <broonie@kernel.org>
> > > Reviewed-by: Julien Grall <julien@xen.org>
> > > Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
> >
> > Thank you!
> >
> > > ---
> > > arch/arm64/xen/hypercall.S | 8 ++++----
> > > 1 file changed, 4 insertions(+), 4 deletions(-)
>
> Is this going via the Xen tree, or shall I queue it along with the other
> asm annotation patches in the arm64 tree? I don't see it in -next yet.
Since it has been reviewed by the Xen maintainers, just queue it via the
arm64 tree.
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-01-09 15:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 12:25 [PATCH v2] arm64: xen: Use modern annotations for assembly functions Mark Brown
2019-12-19 21:07 ` Stefano Stabellini
2020-01-08 15:55 ` Will Deacon
2020-01-09 15:58 ` Catalin Marinas [this message]
2020-01-09 16:33 ` Stefano Stabellini
2020-01-09 16:35 ` Will Deacon
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=20200109155824.GG25655@arrakis.emea.arm.com \
--to=catalin.marinas@arm.com \
--cc=broonie@kernel.org \
--cc=julien@xen.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=sstabellini@kernel.org \
--cc=will@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