From: Mark Brown <broonie@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] arm64/sysreg: Fix a few missed conversions
Date: Mon, 19 Sep 2022 17:22:35 +0100 [thread overview]
Message-ID: <YyiXS0k4EUS0KaZh@sirena.org.uk> (raw)
In-Reply-To: <20220919160928.3905780-1-nathan@kernel.org>
[-- Attachment #1.1: Type: text/plain, Size: 420 bytes --]
On Mon, Sep 19, 2022 at 09:09:28AM -0700, Nathan Chancellor wrote:
> After the conversion to automatically generating the ID_AA64DFR0_EL1
> definition names, the build fails in a few different places because some
> of the definitions were not changed to their new names along the way.
> Update the names to resolve the build errors.
Ah, I was just working on the same fix:
Reviewed-by: Mark Brown <broonie@kernel.org>
[-- 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
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] arm64/sysreg: Fix a few missed conversions
Date: Mon, 19 Sep 2022 17:22:35 +0100 [thread overview]
Message-ID: <YyiXS0k4EUS0KaZh@sirena.org.uk> (raw)
In-Reply-To: <20220919160928.3905780-1-nathan@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 420 bytes --]
On Mon, Sep 19, 2022 at 09:09:28AM -0700, Nathan Chancellor wrote:
> After the conversion to automatically generating the ID_AA64DFR0_EL1
> definition names, the build fails in a few different places because some
> of the definitions were not changed to their new names along the way.
> Update the names to resolve the build errors.
Ah, I was just working on the same fix:
Reviewed-by: Mark Brown <broonie@kernel.org>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-09-19 16:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 16:09 [PATCH -next] arm64/sysreg: Fix a few missed conversions Nathan Chancellor
2022-09-19 16:09 ` Nathan Chancellor
2022-09-19 16:22 ` Mark Brown [this message]
2022-09-19 16:22 ` Mark Brown
2022-09-21 12:04 ` Catalin Marinas
2022-09-21 12:04 ` Catalin Marinas
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=YyiXS0k4EUS0KaZh@sirena.org.uk \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.