linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: kernel test robot <lkp@intel.com>
Cc: Christoph Hellwig <hch@lst.de>,
	kbuild-all@lists.01.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>, Jeremy Kerr <jk@ozlabs.org>
Subject: Re: file.c:undefined reference to `.dump_emit'
Date: Mon, 6 Jul 2020 15:19:40 +0200	[thread overview]
Message-ID: <CAK8P3a2BnecaxYpMzuEHrBqCbA_z0D4Fr=UU_MaFiddZ7OLm=g@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a2dLDf-gOezrzmp0J1ZtnnZgq5KstUO4RZ0Wnfs9J2H_A@mail.gmail.com>

On Mon, Jul 6, 2020 at 3:04 PM Arnd Bergmann <arnd@arndb.de> wrote:
>
> On Mon, Jul 6, 2020 at 12:17 PM kernel test robot <lkp@intel.com> wrote:
> >
> In the interest of keeping things simple, I'd suggest doing this one instead:
>
> --- a/arch/powerpc/platforms/cell/Kconfig
> +++ b/arch/powerpc/platforms/cell/Kconfig
> @@ -44,6 +44,7 @@ config SPU_FS
>         tristate "SPU file system"
>         default m
>         depends on PPC_CELL
> +       depends on COREDUMP
>         select SPU_BASE
>         help
>           The SPU file system is used to access Synergistic Processing
>
> I'll send a proper patch if there are no objections.
>

I see now that it's not even a regression, the report was just about
part of the output now coming from a different file.

I'll send the fix anyway, there is no need for this to be broken.

        Arnd

      reply	other threads:[~2020-07-06 13:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-06 10:13 file.c:undefined reference to `.dump_emit' kernel test robot
2020-07-06 13:04 ` Arnd Bergmann
2020-07-06 13:19   ` Arnd Bergmann [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='CAK8P3a2BnecaxYpMzuEHrBqCbA_z0D4Fr=UU_MaFiddZ7OLm=g@mail.gmail.com' \
    --to=arnd@arndb.de \
    --cc=hch@lst.de \
    --cc=jk@ozlabs.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=viro@zeniv.linux.org.uk \
    /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).