All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 205303] New: Compilation for PPC64 fails on warning in watchdog.o
Date: Thu, 24 Oct 2019 08:23:39 +0000	[thread overview]
Message-ID: <bug-205303-206035@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=205303

            Bug ID: 205303
           Summary: Compilation for PPC64 fails on warning in watchdog.o
           Product: Platform Specific/Hardware
           Version: 2.5
    Kernel Version: 5.3.7
          Hardware: PPC-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: PPC-64
          Assignee: platform_ppc-64@kernel-bugs.osdl.org
          Reporter: payphoneed@gmail.com
        Regression: No

Kernel compilation of 5.3.7 on PowerPC 64bit fails with a compiler warning
treated as an error.

arch/powerpc/kernel/watchdog.c: In function *watchdog_smp_panic*:
arch/powerpc/kernel/watchdog.c:175:4: error: implicit declaration of function
*smp_send_nmi_ipi*: did you mean *smp_send_stop*?
[-Werror=implicit-function-declaration]

SMP and Watchdog Timer Support are both disabled in this kernel configuration.

If additional information is necessary please ask.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2019-10-24  8:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24  8:23 bugzilla-daemon [this message]
2019-10-24  8:33 ` [Bug 205303] Compilation for PPC64 fails on warning in watchdog.o bugzilla-daemon
2019-10-25  8:04 ` bugzilla-daemon
2021-07-23 10:21 ` bugzilla-daemon

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=bug-205303-206035@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    /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.