From: David Miller <davem@davemloft.net>
To: marcel@holtmann.org
Cc: sfr@canb.auug.org.au, kkeil@suse.de,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
akpm@linux-foundation.org, torvalds@linux-foundation.org
Subject: Re: mISDN still breaking the allmodconfig build...
Date: Sun, 27 Jul 2008 18:07:36 -0700 (PDT) [thread overview]
Message-ID: <20080727.180736.74131389.davem@davemloft.net> (raw)
In-Reply-To: <93120C4B-D2F4-4479-806B-2141AC3DC607@holtmann.org>
From: Marcel Holtmann <marcel@holtmann.org>
Date: Mon, 28 Jul 2008 03:03:04 +0200
> > More fallout from the premature mISDN driver merge:
> >
> > drivers/isdn/hardware/mISDN/hfcmulti.c:5255:2: error: #error "not
> > running on big endian machines now"
>
> is that only the HFC driver or the whole mISDN stack?
>
> I know that the two old ISDN stacks where really bad on big endian,
> but my assumption was that we did sort this out in the end.
One of the two mISDN drivers uses the deprecated virt_to_bus()
interface for handling DMA addresses (that doesn't even work on many
x86 systems these days) and the other mISDN driver gives the above
big-endian compile time error.
In short, this driver was not ready for merging at all.
next prev parent reply other threads:[~2008-07-28 1:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 0:02 mISDN still breaking the allmodconfig build David Miller
2008-07-28 0:13 ` Benjamin Herrenschmidt
2008-07-28 0:48 ` Sean MacLennan
2008-07-28 9:20 ` Alan Cox
2008-07-28 11:14 ` Karsten Keil
2008-07-28 1:03 ` Marcel Holtmann
2008-07-28 1:07 ` David Miller [this message]
2008-07-28 1:13 ` Marcel Holtmann
2008-07-28 8:40 ` Karsten Keil
2008-07-28 12:49 ` Sinan Akman
2008-08-04 12:56 ` Karsten Keil
2008-07-28 1:57 ` Mikael Pettersson
2008-07-28 10:26 ` Karsten Keil
2008-07-28 10:50 ` Benjamin Herrenschmidt
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=20080727.180736.74131389.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=kkeil@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=marcel@holtmann.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).