From: Sudeep Holla <sudeep.holla@arm.com>
To: Andrew Scull <ascull@google.com>
Cc: mark.rutland@arm.com, lorenzo.pieralisi@arm.com,
kernel-team@android.com, linux-arm-kernel@lists.infradead.org,
Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH] smccc: Make constants available to assembly
Date: Mon, 6 Jul 2020 18:02:22 +0100 [thread overview]
Message-ID: <20200706170222.GA10953@bogus> (raw)
In-Reply-To: <20200618145511.69203-1-ascull@google.com>
On Thu, Jun 18, 2020 at 03:55:11PM +0100, Andrew Scull wrote:
> Move constants out of the C-only section of the header next to the other
> constants that are available to assembly.
>
FWIW, looks good to me.
Reviewed-by: Sudeep Holla <sudeep.holla@arm.com>
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-07-06 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 14:55 [PATCH] smccc: Make constants available to assembly Andrew Scull
2020-06-29 12:34 ` Andrew Scull
2020-07-03 13:50 ` Will Deacon
2020-07-06 17:02 ` Sudeep Holla [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=20200706170222.GA10953@bogus \
--to=sudeep.holla@arm.com \
--cc=ascull@google.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.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;
as well as URLs for NNTP newsgroup(s).