All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karsten Keil <kkeil@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
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,
	David Miller <davem@davemloft.net>
Subject: Re: mISDN still breaking the allmodconfig build...
Date: Mon, 28 Jul 2008 13:14:58 +0200	[thread overview]
Message-ID: <20080728111458.GA26604@pingi.kke.suse.de> (raw)
In-Reply-To: <20080728102009.5fb3df6b@lxorguk.ukuu.org.uk>

On Mon, Jul 28, 2008 at 10:20:09AM +0100, Alan Cox wrote:
> 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.
> 

This only affect the hardware IO layer of some cards and I think
it will be fixed very soon, I did not remove the very old
#error line, because I did not had the hardware to verify that it is
OK now.
I already reserved a PPC machine now (will get it today or tomorrow) and
will test the endian robustness this week.

> 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 ?
> 

This was my original plan and my fault, that I only included the
pull URL and sent it to Linus diectely, I did not know that in this case
Linus will pull it without further discussion, but I'm still glad that it
is in and only show few issues (I'm very unhappy that I did not find
these before, I did builds on all our architectures, but not with the
all*config, only with subsets).
The good thing is, that this brought back the ENDIAN issue back on my
radar and on my near time TODO list :-)

-- 
Karsten Keil
SuSE Labs
ISDN and VOIP development
SUSE LINUX Products GmbH, Maxfeldstr.5 90409 Nuernberg, GF: Markus Rex, HRB 16746 (AG Nuernberg)

WARNING: multiple messages have this Message-ID (diff)
From: Karsten Keil <kkeil@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
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 13:14:58 +0200	[thread overview]
Message-ID: <20080728111458.GA26604@pingi.kke.suse.de> (raw)
In-Reply-To: <20080728102009.5fb3df6b@lxorguk.ukuu.org.uk>

On Mon, Jul 28, 2008 at 10:20:09AM +0100, Alan Cox wrote:
> 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.
> 

This only affect the hardware IO layer of some cards and I think
it will be fixed very soon, I did not remove the very old
#error line, because I did not had the hardware to verify that it is
OK now.
I already reserved a PPC machine now (will get it today or tomorrow) and
will test the endian robustness this week.

> 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 ?
> 

This was my original plan and my fault, that I only included the
pull URL and sent it to Linus diectely, I did not know that in this case
Linus will pull it without further discussion, but I'm still glad that it
is in and only show few issues (I'm very unhappy that I did not find
these before, I did builds on all our architectures, but not with the
all*config, only with subsets).
The good thing is, that this brought back the ENDIAN issue back on my
radar and on my near time TODO list :-)

-- 
Karsten Keil
SuSE Labs
ISDN and VOIP development
SUSE LINUX Products GmbH, Maxfeldstr.5 90409 Nuernberg, GF: Markus Rex, HRB 16746 (AG Nuernberg)

  reply	other threads:[~2008-07-28 11:15 UTC|newest]

Thread overview: 28+ 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:02 ` David Miller
2008-07-28  0:13 ` Benjamin Herrenschmidt
2008-07-28  0:13   ` Benjamin Herrenschmidt
2008-07-28  0:48   ` Sean MacLennan
2008-07-28  0:48     ` Sean MacLennan
2008-07-28  9:20     ` Alan Cox
2008-07-28  9:20       ` Alan Cox
2008-07-28 11:14       ` Karsten Keil [this message]
2008-07-28 11:14         ` Karsten Keil
2008-07-28  1:03 ` Marcel Holtmann
2008-07-28  1:03   ` Marcel Holtmann
2008-07-28  1:07   ` David Miller
2008-07-28  1:07     ` David Miller
2008-07-28  1:13     ` Marcel Holtmann
2008-07-28  1:13       ` Marcel Holtmann
2008-07-28  8:40       ` Karsten Keil
2008-07-28  8:40         ` Karsten Keil
2008-07-28 12:49         ` Sinan Akman
2008-07-28 12:49           ` Sinan Akman
2008-08-04 12:56           ` Karsten Keil
2008-08-04 12:56             ` Karsten Keil
2008-07-28  1:57     ` Mikael Pettersson
2008-07-28  1:57       ` Mikael Pettersson
2008-07-28 10:26     ` Karsten Keil
2008-07-28 10:26       ` Karsten Keil
2008-07-28 10:50   ` Benjamin Herrenschmidt
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=20080728111458.GA26604@pingi.kke.suse.de \
    --to=kkeil@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.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 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.