All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Joey Gouly <joey.gouly@arm.com>, linux-arm-kernel@lists.infradead.org
Cc: catalin.marinas@arm.com, kernel-team@android.com,
	Will Deacon <will@kernel.org>,
	pcc@google.com, nd@arm.com, mark.rutland@arm.com
Subject: Re: [PATCH v1 -next] kasan: fix a missing header include of static_keys.h
Date: Mon,  7 Mar 2022 22:03:30 +0000	[thread overview]
Message-ID: <164668941526.3276591.16335503450068989347.b4-ty@kernel.org> (raw)
In-Reply-To: <20220301154518.19456-1-joey.gouly@arm.com>

On Tue, 1 Mar 2022 15:45:18 +0000, Joey Gouly wrote:
> The kasan-enabled.h header relies on static keys, so make sure
> to include the header to avoid compilation errors (with JUMP_LABEL=n).
> 
> It fixes the following:
> ./include/linux/kasan-enabled.h:9:1: warning: data definition has no type or storage class
>     9 | DECLARE_STATIC_KEY_FALSE(kasan_flag_enabled);
>       | ^~~~~~~~~~~~~~~~~~~~~~~~
> error: type defaults to 'int' in declaration of 'DECLARE_STATIC_KEY_FALSE' [-Werror=implicit-int]
> 
> [...]

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

[1/1] kasan: fix a missing header include of static_keys.h
      https://git.kernel.org/arm64/c/1a7b2121ebd3

Cheers,
-- 
Will

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

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

  parent reply	other threads:[~2022-03-07 22:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01 15:45 [PATCH v1 -next] kasan: fix a missing header include of static_keys.h Joey Gouly
2022-03-02 11:16 ` Catalin Marinas
2022-03-02 15:25   ` Andrey Konovalov
2022-03-07 22:03 ` Will Deacon [this message]
2022-03-09  9:49   ` Joey Gouly
2022-03-09 12:14     ` 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=164668941526.3276591.16335503450068989347.b4-ty@kernel.org \
    --to=will@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=joey.gouly@arm.com \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=nd@arm.com \
    --cc=pcc@google.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 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.