linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Roland Dreier <rdreier@cisco.com>
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>,
	alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH] isdn: mISDN HFC PCI support depends on virt_to_bus()
Date: Sun, 27 Jul 2008 22:43:55 +0200	[thread overview]
Message-ID: <20080727204355.GA14057@uranus.ravnborg.org> (raw)
In-Reply-To: <adamyk35aoi.fsf@cisco.com>

On Sun, Jul 27, 2008 at 01:33:49PM -0700, Roland Dreier wrote:
>  > IMHO, this driver was really rushed in and that was a huge mistake.
>  > If it had gone through linux-next we could have tidied all of this
>  > stuff up in a less "rushed" manner.
> 
> ??  This thread *is* about a build failure in linux-next.
mISDN are in -linus which is part of -next and Stephens point is that if
we have had mISDN in -next then this would have been fixed before hitting
-linus. Maybe Karsten should use davem as gateway as he has anyway been
so for other isdn patches lately?

	Sam

  reply	other threads:[~2008-07-27 20:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-27 16:37 [PATCH] isdn: mISDN HFC PCI support depends on virt_to_bus() Stephen Rothwell
2008-07-27 17:27 ` Alan Cox
2008-07-27 19:56   ` David Miller
2008-07-27 20:33     ` Roland Dreier
2008-07-27 20:43       ` Sam Ravnborg [this message]
2008-07-28  0:17         ` Stephen Rothwell
2008-07-27 23:14       ` David Miller
2008-07-28  0:20         ` Stephen Rothwell
2008-07-28  0:16       ` Stephen Rothwell
2008-07-28 12:33     ` Christoph Hellwig
2008-07-28  0:15   ` Stephen Rothwell
2008-07-27 17:39 ` Sean MacLennan
2008-07-28  0:23   ` Stephen Rothwell

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=20080727204355.GA14057@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davem@davemloft.net \
    --cc=kkeil@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=rdreier@cisco.com \
    --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).