All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Hellstrom <daniel@gaisler.com>
To: David Miller <davem@davemloft.net>
Cc: sfr@canb.auug.org.au, linux-next@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (sparc-current tree related)
Date: Fri, 03 Jun 2011 09:42:39 +0200	[thread overview]
Message-ID: <4DE8906F.5040501@gaisler.com> (raw)
In-Reply-To: <20110602.222051.270790327969020201.davem@davemloft.net>

David Miller wrote:

>From: Stephen Rothwell <sfr@canb.auug.org.au>
>Date: Fri, 3 Jun 2011 13:53:47 +1000
>
>  
>
>>Caused by commit cfe3af5dde34 ("sparc32: added CONFIG_PCIC_PCI Kconfig
>>setting") from the sparc-current tree.
>>
>>I have reverted that commit (and the 2 following commits that depend on
>>it) for today.
>>    
>>
>
>Oops, that needs a sparc32 depencency.  I'll fix that, thanks!
>  
>
missed that, PCIC_PCI should depend on SPARC32_PCI instead of PCI in the 
following lines that were added by the patch

+config PCIC_PCI
+	bool
+	depends on PCI && !SPARC_LEON
+	default y
+

  reply	other threads:[~2011-06-03  7:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-03  3:53 linux-next: build failure after merge of the final tree (sparc-current tree related) Stephen Rothwell
2011-06-03  5:20 ` David Miller
2011-06-03  7:42   ` Daniel Hellstrom [this message]
2011-06-03  8:14     ` David Miller
2011-06-03 12:26       ` Daniel Hellstrom
  -- strict thread matches above, loose matches on Subject: below --
2011-03-31  2:01 Stephen Rothwell
2011-03-31  4:10 ` David Miller
2011-03-31 13:46   ` Daniel Hellstrom

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=4DE8906F.5040501@gaisler.com \
    --to=daniel@gaisler.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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 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.