public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>
Cc: dougthompson@xmission.com, mchehab@osg.samsung.com,
	linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
	fengguang.wu@intel.com, kbuild-all@01.org
Subject: Re: [PATCH] EDAC, mce_amd_inj: Include irq_vectors header to fix build errors
Date: Sat, 6 Jun 2015 09:50:50 +0200	[thread overview]
Message-ID: <20150606075050.GA545@pd.tnic> (raw)
In-Reply-To: <1433545654-24450-1-git-send-email-Aravind.Gopalakrishnan@amd.com>

On Fri, Jun 05, 2015 at 06:07:34PM -0500, Aravind Gopalakrishnan wrote:
> Even though !CONFIG_SMP and MCE injection are practically mutually
> exclusive, it's better to include irq_vectors.h just in case
> randconfig builders out there don't set CONFIG_SMP.
> 
> When that happens, DEFERRED_ERROR_VECTOR and THRESHOLD_APIC_VECTOR
> macro definitions go out of scope and kernel build will fail.

Good!

> Tested the .config that broke the build against latest tip with
> changes in for-next branch of bp.git and it builds fine now.
> 
> Reported-by: kbuild test robot <fengguang.wu@intel.com>
> Cc: kbuild-all@01.org
> Signed-off-by: Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>
> ---
>  drivers/edac/mce_amd_inj.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/edac/mce_amd_inj.c b/drivers/edac/mce_amd_inj.c
> index 3f7217f..3e1b53f 100644
> --- a/drivers/edac/mce_amd_inj.c
> +++ b/drivers/edac/mce_amd_inj.c
> @@ -18,6 +18,7 @@
>  #include <linux/string.h>
>  #include <linux/uaccess.h>
>  #include <asm/mce.h>
> +#include <asm/irq_vectors.h>
>  
>  #include "mce_amd.h"

Applied, thanks.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--

      reply	other threads:[~2015-06-06  7:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-05 23:07 [PATCH] EDAC, mce_amd_inj: Include irq_vectors header to fix build errors Aravind Gopalakrishnan
2015-06-06  7:50 ` Borislav Petkov [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=20150606075050.GA545@pd.tnic \
    --to=bp@alien8.de \
    --cc=Aravind.Gopalakrishnan@amd.com \
    --cc=dougthompson@xmission.com \
    --cc=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@osg.samsung.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