All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Miller <davem@davemloft.net>
Cc: sfr@canb.auug.org.au, paulus@samba.org,
	linuxppc-dev@lists.ozlabs.org, mika.westerberg@linux.intel.com,
	netdev@vger.kernel.org, linux-next@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (net-next tree related)
Date: Sun, 23 Sep 2012 07:20:07 +1000	[thread overview]
Message-ID: <1348348807.1132.76.camel@pasglop> (raw)
In-Reply-To: <20120922.160027.1528491047223302539.davem@davemloft.net>

On Sat, 2012-09-22 at 16:00 -0400, David Miller wrote:
> 
> I think I'm going to just end up restricting this driver to X86
> as was originally suggested.

Probably the easiest fix indeed.

> There seems to be no real consistent Kconfig protection for users
> of isa_virt_to_bus() and friends.
> 
> We know that ISA_DMA_API doesn't do it, and ISA doesn't do it either
> as powerpc also allows that to bet set for CHRP and friends.

It's a old mess :-( And not an easy one to untangle...

Cheers,
Ben.

WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Miller <davem@davemloft.net>
Cc: sfr@canb.auug.org.au, mika.westerberg@linux.intel.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-next@vger.kernel.org, paulus@samba.org,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: linux-next: build failure after merge of the final tree (net-next tree related)
Date: Sun, 23 Sep 2012 07:20:07 +1000	[thread overview]
Message-ID: <1348348807.1132.76.camel@pasglop> (raw)
In-Reply-To: <20120922.160027.1528491047223302539.davem@davemloft.net>

On Sat, 2012-09-22 at 16:00 -0400, David Miller wrote:
> 
> I think I'm going to just end up restricting this driver to X86
> as was originally suggested.

Probably the easiest fix indeed.

> There seems to be no real consistent Kconfig protection for users
> of isa_virt_to_bus() and friends.
> 
> We know that ISA_DMA_API doesn't do it, and ISA doesn't do it either
> as powerpc also allows that to bet set for CHRP and friends.

It's a old mess :-( And not an easy one to untangle...

Cheers,
Ben.

  reply	other threads:[~2012-09-22 21:21 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20  7:36 linux-next: build failure after merge of the final tree (net-next tree related) Stephen Rothwell
2012-09-20  7:36 ` Stephen Rothwell
2012-09-20  9:10 ` Mika Westerberg
2012-09-20 20:45   ` David Miller
2012-09-20 22:15     ` Stephen Rothwell
2012-09-20 22:15       ` Stephen Rothwell
2012-09-20 22:15       ` Stephen Rothwell
2012-09-20 22:22       ` Benjamin Herrenschmidt
2012-09-20 22:22         ` Benjamin Herrenschmidt
2012-09-20 22:53         ` David Miller
2012-09-20 22:53           ` David Miller
2012-09-21 21:46           ` Benjamin Herrenschmidt
2012-09-21 21:46             ` Benjamin Herrenschmidt
2012-09-22 20:00             ` David Miller
2012-09-22 20:00               ` David Miller
2012-09-22 21:20               ` Benjamin Herrenschmidt [this message]
2012-09-22 21:20                 ` Benjamin Herrenschmidt
2012-09-20 22:28     ` Stephen Rothwell
2012-09-20 22:28       ` Stephen Rothwell
2012-09-20 22:28       ` Stephen Rothwell
2012-09-21  1:37 ` Stephen Rothwell
2012-09-21  1:37   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2014-03-18  7:27 Stephen Rothwell
2014-03-18  7:27 ` Stephen Rothwell
2014-03-19  3:13 ` David Miller
2014-03-17 10:21 Stephen Rothwell
2014-03-17 10:21 ` Stephen Rothwell
2014-03-19  3:11 ` David Miller
2014-03-17 10:13 Stephen Rothwell
2014-03-17 10:13 ` Stephen Rothwell
2013-09-02  9:11 Stephen Rothwell
2013-09-02  9:11 ` Stephen Rothwell
2013-09-02  9:18 ` Cong Wang
2013-07-03  7:48 Stephen Rothwell
2013-07-03  7:48 ` Stephen Rothwell
2013-07-03  7:51 ` Sedat Dilek
2013-07-03  8:45 ` Eliezer Tamir
2013-07-03 19:17 ` David Miller
2013-06-26  7:56 Stephen Rothwell
2013-06-26  7:56 ` Stephen Rothwell
2013-06-26  8:07 ` Alexey Brodkin
2013-06-26  8:36   ` David Miller
2013-04-23  7:46 Stephen Rothwell
2013-04-23  7:46 ` Stephen Rothwell
2013-04-23 17:10 ` David Miller
2013-04-23 23:44 ` David Rientjes
2013-04-12  6:00 Stephen Rothwell
2013-04-12  6:00 ` Stephen Rothwell
2013-04-12  7:08 ` David Miller
2013-03-28  5:04 Stephen Rothwell
2013-03-28  5:04 ` Stephen Rothwell
2013-03-28  5:19 ` David Miller
2013-01-03  3:23 Stephen Rothwell
2013-01-03  3:23 ` Stephen Rothwell
2013-01-03  3:28 ` David Miller
2013-01-03  9:51 ` David Miller
2012-09-05  5:39 Stephen Rothwell
2012-09-05  5:39 ` Stephen Rothwell
2012-09-05 21:46 ` David Miller
2012-09-04  6:58 Stephen Rothwell
2012-09-04 18:20 ` David Miller
2012-09-04 19:50   ` Jerry Chu
2012-07-22  6:34 Stephen Rothwell
2012-07-22  7:29 ` Jiri Pirko
2012-05-03  6:16 Stephen Rothwell
2012-05-03  6:16 ` Stephen Rothwell
2012-05-03  6:26 ` David Miller
2012-04-30  5:58 Stephen Rothwell
2012-04-30  5:58 ` Stephen Rothwell
2012-04-30 17:22 ` David Miller
2012-04-19  6:28 Stephen Rothwell
2012-04-19  6:28 ` Stephen Rothwell
2012-04-19  6:40 ` David Miller
2012-04-10  5:29 Stephen Rothwell
2012-04-10  5:29 ` Stephen Rothwell
2012-04-10 13:26 ` David Miller
2012-04-05  3:25 Stephen Rothwell
2012-04-05  3:25 ` Stephen Rothwell
2012-04-05  3:59 ` David Miller
2012-04-06  7:09   ` Giuseppe CAVALLARO
2012-04-06  7:30     ` Giuseppe CAVALLARO
2012-02-20  5:15 Stephen Rothwell
2012-02-20  5:15 ` Stephen Rothwell
2012-02-20  5:46 ` David Miller
2011-12-14  7:07 Stephen Rothwell
2011-12-14  7:07 ` Stephen Rothwell
2011-12-14 18:35 ` David Miller
2011-11-23  4:00 Stephen Rothwell
2011-11-23  4:00 ` Stephen Rothwell
2011-11-23 12:09 ` Neil Horman
2011-11-23 23:02   ` Andrew Morton
2011-11-23 23:44     ` David Miller

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=1348348807.1132.76.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=paulus@samba.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.