public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat•com>
To: Vignesh Balasubramanian <vigbalas@amd•com>
Cc: felix.willgerodt@intel•com, matz@suse•de, keescook@chromium•org,
	jhb@FreeBSD•org, bpetkov@amd•com, binutils@sourceware•org,
	x86@kernel•org, linux-kernel@vger•kernel.org,
	aneesh.kumar@kernel•org, linux-mm@kvack•org, npiggin@gmail•com,
	linux-toolchains@vger•kernel.org, naveen.n.rao@linux•ibm.com,
	linuxppc-dev@lists•ozlabs.org, jinisusan.george@amd•com,
	ebiederm@xmission•com
Subject: Re: [PATCH 1/1] Replace macro "ARCH_HAVE_EXTRA_ELF_NOTES" with kconfig
Date: Mon, 22 Apr 2024 10:15:44 +0200	[thread overview]
Message-ID: <874jbt7qz3.fsf@oldenburg3.str.redhat.com> (raw)
In-Reply-To: <20240412062138.1132841-2-vigbalas@amd.com> (Vignesh Balasubramanian's message of "Fri, 12 Apr 2024 11:51:39 +0530")

* Vignesh Balasubramanian:

> diff --git a/include/linux/elf.h b/include/linux/elf.h
> index c9a46c4e183b..5c402788da19 100644
> --- a/include/linux/elf.h
> +++ b/include/linux/elf.h
> @@ -65,7 +65,7 @@ extern Elf64_Dyn _DYNAMIC [];
>  struct file;
>  struct coredump_params;
>  
> -#ifndef ARCH_HAVE_EXTRA_ELF_NOTES
> +#ifndef CONFIG_ARCH_HAVE_EXTRA_ELF_NOTES

You could add

  #pragma GCC poison ARCH_HAVE_EXTRA_ELF_NOTES

to a central header, to let GCC and Clang flag uses that have not been
converted.

Thanks,
Florian


  parent reply	other threads:[~2024-04-22  8:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-12  6:21 [PATCH 0/1] Replace the macro "ARCH_HAVE_EXTRA_ELF_NOTES" with kconfig Vignesh Balasubramanian
2024-04-12  6:21 ` [PATCH 1/1] Replace " Vignesh Balasubramanian
2024-04-12 12:07   ` Michael Ellerman
2024-04-22  8:15   ` Florian Weimer [this message]
2024-04-15 18:03 ` [PATCH 0/1] Replace the " Kees Cook

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=874jbt7qz3.fsf@oldenburg3.str.redhat.com \
    --to=fweimer@redhat$(echo .)com \
    --cc=aneesh.kumar@kernel$(echo .)org \
    --cc=binutils@sourceware$(echo .)org \
    --cc=bpetkov@amd$(echo .)com \
    --cc=ebiederm@xmission$(echo .)com \
    --cc=felix.willgerodt@intel$(echo .)com \
    --cc=jhb@FreeBSD$(echo .)org \
    --cc=jinisusan.george@amd$(echo .)com \
    --cc=keescook@chromium$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-mm@kvack$(echo .)org \
    --cc=linux-toolchains@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=matz@suse$(echo .)de \
    --cc=naveen.n.rao@linux$(echo .)ibm.com \
    --cc=npiggin@gmail$(echo .)com \
    --cc=vigbalas@amd$(echo .)com \
    --cc=x86@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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