public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Tony Luck <tony.luck@intel.com>,
	Fenghua Yu <fenghua.yu@intel.com>, Tom Vaden <tom.vaden@hpe.com>,
	Daisuke HATAYAMA <d.hatayama@jp.fujitsu.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: kbuild-all@lists.01.org, Joerg Roedel <jroedel@suse.de>,
	stable@vger.kernel.org
Subject: Re: [RFT PATCH] ia64: Fix build error with !COREDUMP
Date: Tue, 07 Jul 2020 18:34:59 +0000	[thread overview]
Message-ID: <20200707183459.GB3442@kozik-lap> (raw)
In-Reply-To: <20200604201842.29482-1-krzk@kernel.org>

On Thu, Jun 04, 2020 at 10:18:42PM +0200, Krzysztof Kozlowski wrote:
> Fix linkage error when CONFIG_BINFMT_ELF is selected but CONFIG_COREDUMP
> is not:
> 
>     ia64-linux-ld: arch/ia64/kernel/elfcore.o: in function `elf_core_write_extra_phdrs':
>     elfcore.c:(.text+0x172): undefined reference to `dump_emit'
>     ia64-linux-ld: arch/ia64/kernel/elfcore.o: in function `elf_core_write_extra_data':
>     elfcore.c:(.text+0x2b2): undefined reference to `dump_emit'
> 
> Cc: <stable@vger.kernel.org>
> Fixes: 1fcccbac89f5 ("elf coredump: replace ELF_CORE_EXTRA_* macros by functions")
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
> 
> ---
> 
> Please let kbuild test it for a while before applying. I built it only
> on few configurations.
> 
> This is similar fix to commit 42d91f612c87 ("um: Fix build error and
> kconfig for i386") although I put different fixes tag - the commit which
> introduced this part of code.

Kernel-test-robot did not complain anymore so I think build tests
passed.

Any comments here?

Best regards,
Krzysztof

      reply	other threads:[~2020-07-07 18:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-04 20:18 [RFT PATCH] ia64: Fix build error with !COREDUMP Krzysztof Kozlowski
2020-07-07 18:34 ` Krzysztof Kozlowski [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=20200707183459.GB3442@kozik-lap \
    --to=krzk@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=d.hatayama@jp.fujitsu.com \
    --cc=fenghua.yu@intel.com \
    --cc=jroedel@suse.de \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tom.vaden@hpe.com \
    --cc=tony.luck@intel.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