public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Zhuo, Qiuxu" <qiuxu.zhuo@intel.com>,
	Nicholas Piggin <npiggin@gmail.com>
Subject: RE: linux-next: Tree for Nov 19 (drivers/edac/igen6_edac.c)
Date: Thu, 19 Nov 2020 17:53:33 +0000	[thread overview]
Message-ID: <0ad9aeffcd5342f59bae6fe64218d011@intel.com> (raw)
In-Reply-To: <6d36cd23-2647-f3b1-5f55-1e00105698eb@infradead.org>

> ../drivers/edac/igen6_edac.c: In function 'ecclog_nmi_handler':
> ../drivers/edac/igen6_edac.c:525:10: error: 'NMI_DONE' undeclared (first use in this function); did you mean 'DMI_NONE'?
>    return NMI_DONE;

This driver has a #include <linux/nmi.h>

But inside that file it says:

#if defined(CONFIG_HAVE_NMI_WATCHDOG)
#include <asm/nmi.h>
#endif

and the randconfig used doesn't set CONFIG_HAVE_NMI_WATCHDOG


Some options:

1) Drop that #ifdef from <linux/nmi.h>
It was introduced as part of this commit:
f2e0cff85ed1 ("kernel/watchdog: introduce arch_touch_nmi_watchdog()")
presumably for some good reason.

2) Make this edac driver select CONFIG_HAVE_NMI_WATCHDOG
Yuck!

3) Make this driver #include <asm/nmi.h> instead of <linux/nmi.h>
This fixes this build error, but I thought that general policy was to
use the <linux/*.h> if it exists rather than the <asm/*.h> one.
Maybe that's ok here because this is an x86 specific driver?

I'm leaning toward option #3.

-Tony

  reply	other threads:[~2020-11-19 17:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19  6:08 linux-next: Tree for Nov 19 Stephen Rothwell
2020-11-19 16:49 ` linux-next: Tree for Nov 19 (drivers/edac/igen6_edac.c) Randy Dunlap
2020-11-19 17:53   ` Luck, Tony [this message]
2020-11-19 18:12     ` Randy Dunlap

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=0ad9aeffcd5342f59bae6fe64218d011@intel.com \
    --to=tony.luck@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=npiggin@gmail.com \
    --cc=qiuxu.zhuo@intel.com \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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