mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Nemanja Rakovic <nemanja.rakovic@syrmia.com>
Cc: linux-kernel@vger.kernel.org, dragan.mladjenovic@syrmia.com,
	elver@google.com
Subject: Re: [PATCH V3] mips-next: Enable KCSAN
Date: Tue, 22 Feb 2022 09:45:49 +0100	[thread overview]
Message-ID: <20220222084549.GB7049@alpha.franken.de> (raw)
In-Reply-To: <20220221121225.8699-1-nemanja.rakovic@syrmia.com>

On Mon, Feb 21, 2022 at 01:12:25PM +0100, Nemanja Rakovic wrote:
> Replaces KASAN_SANITIZE with KCSAN_SANITIZE in
> boot/compressed/Makefile.
> 
> Fixes: e0a8b93efa23 mips: Enable KCSAN
> Signed-off-by: Nemanja Rakovic <nemanja.rakovic@syrmia.com>
> ---
>  arch/mips/boot/compressed/Makefile | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/mips/boot/compressed/Makefile b/arch/mips/boot/compressed/Makefile
> index a35f78212ea9..6cc28173bee8 100644
> --- a/arch/mips/boot/compressed/Makefile
> +++ b/arch/mips/boot/compressed/Makefile
> @@ -38,7 +38,7 @@ KBUILD_AFLAGS := $(KBUILD_AFLAGS) -D__ASSEMBLY__ \
>  KCOV_INSTRUMENT		:= n
>  GCOV_PROFILE := n
>  UBSAN_SANITIZE := n
> -KASAN_SANITIZE			:= n
> +KCSAN_SANITIZE			:= n
>  
>  # decompressor objects (linked with vmlinuz)
>  vmlinuzobjs-y := $(obj)/head.o $(obj)/decompress.o $(obj)/string.o $(obj)/bswapsi.o
> -- 
> 2.17.1

applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      reply	other threads:[~2022-02-22  8:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-21 12:12 Nemanja Rakovic
2022-02-22  8:45 ` Thomas Bogendoerfer [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=20220222084549.GB7049@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=dragan.mladjenovic@syrmia.com \
    --cc=elver@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nemanja.rakovic@syrmia.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

all inboxes | Powered by JetHome®