linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Amit Daniel Kachhap <amit.kachhap@arm.com>,
	linux-arm-kernel@lists.infradead.org
Cc: catalin.marinas@arm.com, kernel-team@android.com,
	Will Deacon <will@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Vincenzo Frascino <Vincenzo.Frascino@arm.com>,
	Kevin Brodsky <kevin.brodsky@arm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] arm64/traps: Avoid unnecessary kernel/user pointer conversion
Date: Wed, 29 Sep 2021 18:48:22 +0100	[thread overview]
Message-ID: <163293026050.926465.15015359578646677100.b4-ty@kernel.org> (raw)
In-Reply-To: <20210917055811.22341-1-amit.kachhap@arm.com>

On Fri, 17 Sep 2021 11:28:11 +0530, Amit Daniel Kachhap wrote:
> Annotating a pointer from kernel to __user and then back again requires
> an extra __force annotation to silent sparse warning. In call_undef_hook()
> this unnecessary complexity can be avoided by modifying the intermediate
> user pointer to unsigned long.
> 
> This way there is no inter-changeable use of user and kernel pointers
> and the code is consistent.
> 
> [...]

Applied to arm64 (for-next/misc), thanks!

[1/1] arm64/traps: Avoid unnecessary kernel/user pointer conversion
      https://git.kernel.org/arm64/c/f5b650f887f3

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev

      parent reply	other threads:[~2021-09-29 17:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-17  5:58 [PATCH v2] arm64/traps: Avoid unnecessary kernel/user pointer conversion Amit Daniel Kachhap
2021-09-17  9:36 ` Mark Rutland
2021-09-29 17:48 ` Will Deacon [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=163293026050.926465.15015359578646677100.b4-ty@kernel.org \
    --to=will@kernel.org \
    --cc=Vincenzo.Frascino@arm.com \
    --cc=amit.kachhap@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=kernel-team@android.com \
    --cc=kevin.brodsky@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --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).