linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: kernel: Correct annotation of end of el0_sync
Date: Fri, 10 Jan 2020 15:53:26 +0000	[thread overview]
Message-ID: <20200110155322.GD5889@sirena.org.uk> (raw)
In-Reply-To: <20200110155004.3577-1-broonie@kernel.org>


[-- Attachment #1.1: Type: text/plain, Size: 642 bytes --]

On Fri, Jan 10, 2020 at 03:50:04PM +0000, Mark Brown wrote:
> Commit 582f95835a8fc812c (arm64: entry: convert el0_sync to C) caused the
> ENDPROC() annotating the end of el0_sync to be placed after the code for
> el0_sync_compat. This replaced the previous annotation where it was
> located after all the cases that are now converted to C, including after
> the currently unannotated el0_irq_compat and el0_error_compat. Move the
> annotation to the end of the function and add separate annotations for the
> _compat ones.

Sorry, just realized that a variant of this is in the series that Mark
posted earlier this week - please ignore this.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-01-10 15:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-10 15:50 [PATCH] arm64: kernel: Correct annotation of end of el0_sync Mark Brown
2020-01-10 15:53 ` Mark Brown [this message]
2020-01-10 15:55   ` Mark Rutland
2020-01-10 15:54 ` Mark Rutland

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=20200110155322.GD5889@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=will@kernel.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).