From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Sean MacLennan <smaclennan@pikatech.com>
Cc: <benh@kernel.crashing.org>, "David Miller" <davem@davemloft.net>,
<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: Mon, 28 Jul 2008 10:20:09 +0100 [thread overview]
Message-ID: <20080728102009.5fb3df6b@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20080727204805.59f55dda@lappy.seanm.ca>
On Sun, 27 Jul 2008 20:48:05 -0400
Sean MacLennan <smaclennan@pikatech.com> wrote:
> On Mon, 28 Jul 2008 10:13:42 +1000
> "Benjamin Herrenschmidt" <benh@kernel.crashing.org> wrote:
>
> > On Sun, 2008-07-27 at 17:02 -0700, David Miller wrote:
> > > 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"
> >
> > Lovely...
>
> mISDN is notoriously bad on big endian machines.
In which case it really should not be in Linus tree but in linux-next.
Karsten - will you ask Linus to revert mISDN so it can go into linux-next
instead and get cleaned up in the right place ?
Alan
next prev parent reply other threads:[~2008-07-28 9:38 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 [this message]
2008-07-28 11:14 ` Karsten Keil
2008-07-28 1:03 ` Marcel Holtmann
2008-07-28 1:07 ` David Miller
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=20080728102009.5fb3df6b@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=kkeil@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sfr@canb.auug.org.au \
--cc=smaclennan@pikatech.com \
--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