public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: bhelgaas@google.com, benh@kernel.crashing.org,
	daniel.price@gmail.com, thierry.reding@gmail.com,
	linux-kernel@vger.kernel.org, jason@lakedaemon.net,
	x86@kernel.org
Subject: Re: Build (x86, i386, non-SMP) breaks due to commit ebd97be635bff43239f391a49c78b98818c589fe (PCI: remove ARCH_SUPPORTS_MSI kconfig option
Date: Mon, 30 Sep 2013 20:07:21 +0200	[thread overview]
Message-ID: <20130930200721.4aed1e40@skate> (raw)
In-Reply-To: <20130930171849.GW3106@phenom.dumpdata.com>

Dear Konrad Rzeszutek Wilk,

On Mon, 30 Sep 2013 13:18:49 -0400, Konrad Rzeszutek Wilk wrote:

> git bisect tells me that
> 
> git commit ebd97be635bff43239f391a49c78b98818c589fe is the first bad commit
> commit ebd97be635bff43239f391a49c78b98818c589fe
> Author: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Date:   Fri Aug 9 22:27:07 2013 +0200
> 
>     PCI: remove ARCH_SUPPORTS_MSI kconfig option
>     
> 
> When I try to build under i386, with make defconfig + # CONFIG_SMP is not set
> I end up with:

Thanks for reporting, I'll have a look tomorrow morning and get back to
you with a patch.

Thanks!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2013-09-30 18:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-30 17:18 Build (x86, i386, non-SMP) breaks due to commit ebd97be635bff43239f391a49c78b98818c589fe (PCI: remove ARCH_SUPPORTS_MSI kconfig option Konrad Rzeszutek Wilk
2013-09-30 18:07 ` Thomas Petazzoni [this message]
2013-10-03  9:59 ` [PATCH] x86: fix PCI_MSI build on !SMP Thomas Petazzoni
2013-10-04 13:57   ` Konrad Rzeszutek Wilk
2013-10-04 17:36   ` Bjorn Helgaas
2013-10-04 17:39     ` H. Peter Anvin
2013-10-04 18:18   ` [tip:x86/urgent] x86, build, pci: Fix " tip-bot for Thomas Petazzoni

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=20130930200721.4aed1e40@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=benh@kernel.crashing.org \
    --cc=bhelgaas@google.com \
    --cc=daniel.price@gmail.com \
    --cc=jason@lakedaemon.net \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox