From: Adrian Bunk <bunk@stusta.de>
To: Tilman Schmidt <tilman@imap.cc>
Cc: Andrew Morton <akpm@osdl.org>, Hansjoerg Lipp <hjlipp@web.de>,
linux-kernel@vger.kernel.org, kkeil@suse.de,
kai.germaschewski@gmx.de, isdn4linux@listserv.isdn4linux.de
Subject: Re: 2.6.16-rc3-mm1: ISDN_DRV_GIGASET driver
Date: Wed, 15 Feb 2006 23:10:46 +0100 [thread overview]
Message-ID: <20060215221046.GC5066@stusta.de> (raw)
In-Reply-To: <43F28A6D.5080109@imap.cc>
On Wed, Feb 15, 2006 at 02:57:01AM +0100, Tilman Schmidt wrote:
> Adrian,
Hi Tilman,
> thank you very much for taking the time to comment.
>
> On 14.02.2006 15:00, you wrote:
> > - Do we really want to add new non-CAPI drivers to the kernel?
>
> I have been in contact with the isdn4linux maintainer Karsten Keil on
> that topic for quite some time and he didn't voice any objections to
> submitting the driver in its current state.
>
> Personally I am a great fan of CAPI, and of course we'll be happy to
> port the driver to CAPI as soon as the capi4linux / mISDN framework is
> ready for such an endeavour. This may however take some time yet, if I
> understand Karsten correctly. In particular, we are talking here about
> the mISDN L3 interface which seems to be the most appropriate for this
> purpose, but has not been documented so far.
>
> In the meantime, I take it from the discussions on lkml that it is
> strongly discouraged to maintain working drivers outside the kernel
> tree, which is what prompted us to submit ours in the first place.
> Therefore I think it's in the best interest of everybody to merge its
> current isnd4linux gestalt now, and convert it to CAPI at the earliest
> convenience.
OK.
> > - A new driver that can only be built modular is not acceptable.
>
> No problem. In fact, the submitted drivers work fine if linked directly
> into the kernel, too. The dependency on modular build in gigaset/Kconfig
> only exists for the benefit of the ser_gigaset driver which we didn't
> submit anyway. (See part 0 for the reasons.) We left it in because tests
> have been done almost exclusively with modular builds; but if that turns
> out to be a problem we'll just remove it.
All drivers in the kernel should work built statically into the kernel,
and I don't see an obvious reason why your driver should work worse when
being compiled statically into the kernel.
> Regards
> Tilman
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-02-15 22:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 9:41 2.6.16-rc3-mm1 Andrew Morton
2006-02-14 11:07 ` 2.6.16-rc3-mm1 Marc Koschewski
2006-02-14 11:16 ` 2.6.16-rc3-mm1 Michal Piotrowski
2006-02-14 12:16 ` 2.6.16-rc3-mm1 Sander
2006-02-14 12:46 ` 2.6.16-rc3-mm1 Michal Piotrowski
2006-02-14 13:17 ` 2.6.16-rc3-mm1: i386 compilation broken Adrian Bunk
2006-02-14 13:27 ` Andi Kleen
2006-02-14 13:54 ` Michal Piotrowski
2006-02-14 20:23 ` Andrew Morton
2006-02-14 21:05 ` Andi Kleen
2006-02-14 21:08 ` Adrian Bunk
2006-02-15 13:19 ` Roman Zippel
2006-02-15 13:32 ` Andi Kleen
2006-02-14 14:00 ` 2.6.16-rc3-mm1: ISDN_DRV_GIGASET driver Adrian Bunk
2006-02-15 1:57 ` Tilman Schmidt
2006-02-15 22:10 ` Adrian Bunk [this message]
2006-02-14 14:33 ` 2.6.16-rc3-mm1 Brice Goglin
2006-02-14 20:28 ` 2.6.16-rc3-mm1 Andrew Morton
2006-02-14 23:26 ` 2.6.16-rc3-mm1 Con Kolivas
2006-02-14 23:38 ` 2.6.16-rc3-mm1 Brice Goglin
2006-02-15 2:58 ` 2.6.16-rc3-mm1 Andrew Morton
2006-02-14 15:22 ` [-mm patch] block/blktrace.c: make blk_trace_cleanup() static Adrian Bunk
2006-02-14 15:23 ` Jens Axboe
2006-02-16 23:28 ` 2.6.16-rc3-mm1 Pavel Machek
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=20060215221046.GC5066@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=hjlipp@web.de \
--cc=isdn4linux@listserv.isdn4linux.de \
--cc=kai.germaschewski@gmx.de \
--cc=kkeil@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tilman@imap.cc \
/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