From: Karsten Keil <kkeil@suse.de>
To: Jeff Garzik <jeff@garzik.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
kai.germaschewski@gmx.de, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ISDN: move card state init to separate function
Date: Tue, 22 May 2007 19:28:27 +0200 [thread overview]
Message-ID: <20070522172827.GA8821@pingi.kke.suse.de> (raw)
In-Reply-To: <46531E58.6030506@garzik.org>
On Tue, May 22, 2007 at 12:46:16PM -0400, Jeff Garzik wrote:
> Karsten Keil wrote:
> >So what is the reason to do this now, does this block some changes in
> >other places ? I did not change this code for long time because I know
> >that this is a nightmare, the code was grown and grown (supporting more and
> >more cards/chipsets) and is really nothing which should be used in future.
> >So I would say it maybe better, if it doesn't block anything else, to
> >replace HiSax completely with a new modular design. I know that here was
> >not
> >so much effort in the past years, but now I got some time to push mISDN
> >forward and it looks not so bad to get the first parts ready for mainline
> >in June.
>
> ISDN is the biggest chunk of code blocking removal of some deprecated
> PCI interfaces.
>
OK then this should be done of course, since I fear that we will not
move all supported cards (since they are not longer sold) to the new driver.
> If you want to replace the code completely with a newfangled modular
> design, I will gladly step out of the way and let that happen :) I only
> know what I see right now, which is code that has sat around for a while
> not getting updated to the new PCI API.
>
> Since I do not have any ISDN hardware, my plan was to do equivalent
> transformations of the code. Each patch just shuffles code, but
> maintains a working state at all time, making it trivial to prove
> (mathematically, or with testing, or with git-bisect) that the code
> continues to work.
So maybe it could be a good start point to do the transition for one
card first, maybe nj_s.c is OK to start.
>
> So, just tell me which you would prefer. If you are going to fix all
> this stuff, there is plenty of other stuff on my list to work on.
> Otherwise I will create equivalent-transform patches that take the
> existing code and modify it just enough to be correct for the new PCI API.
>
If you do that for one card, I will test it and change the rest.
Thanks for your help.
--
Karsten Keil
SuSE Labs
ISDN and VOIP development
SUSE LINUX Products GmbH, Maxfeldstr.5 90409 Nuernberg, GF: Markus Rex, HRB 16746 (AG Nuernberg)
prev parent reply other threads:[~2007-05-22 17:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 12:44 Jeff Garzik
2007-05-22 15:18 ` Karsten Keil
2007-05-22 16:46 ` Jeff Garzik
2007-05-22 17:28 ` Karsten Keil [this message]
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=20070522172827.GA8821@pingi.kke.suse.de \
--to=kkeil@suse.de \
--cc=akpm@linux-foundation.org \
--cc=jeff@garzik.org \
--cc=kai.germaschewski@gmx.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®