From: Adam Belay <ambx1@neo.rr.com>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Jaroslav Kysela <perex@suse.cz>, Adrian Bunk <bunk@fs.tum.de>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Zwane Mwaikambo <zwane@holomorphy.com>
Subject: Re: Linux v2.5.54
Date: Thu, 2 Jan 2003 13:26:40 +0000 [thread overview]
Message-ID: <20030102132640.GA328@neo.rr.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0301021827160.649-100000@pnote.perex-int.cz>
On Thu, Jan 02, 2003 at 06:31:08PM +0100, Jaroslav Kysela wrote:
> On Thu, 2 Jan 2003, Adrian Bunk wrote:
>
> > On Wed, Jan 01, 2003 at 07:43:40PM -0800, Linus Torvalds wrote:
> >
> > >...
> > > Summary of changes from v2.5.53 to v2.5.54
> > > ============================================
> > >...
> > > Jaroslav Kysela <perex@suse.cz>:
> > > o PnP update
> > >...
> >
> > FYI:
> >
> > This change broke the compilation of drivers/ide/ide-pnp.c:
>
> Yes, this code was not functional (although compilable). I've noted this
> situation in my patch comment. We have to upgrade all old ISA PnP code to
> the new PnP layer. It's better to fail with an error than silently ignore
> this situation (this will force more developers to update their parts).
>
> I'll update our ALSA code ASAP.
>
> Jaroslav
>
Zwane has released a patch to convert pnp-ide to the new APIs. I'll send
it out soon but there are pnp ide problems, found in both 2.4 and 2.5, that
need to be resolved. I believe a fix for them will also be out soon. If
anyone has questions about converting drivers feel free to contact me.
Adam
next prev parent reply other threads:[~2003-01-02 18:19 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-02 3:43 Linux v2.5.54 Linus Torvalds
2003-01-02 4:38 ` William Lee Irwin III
2003-01-02 10:43 ` Rusty Russell
2003-01-02 10:55 ` Andi Kleen
2003-01-02 11:13 ` William Lee Irwin III
2003-01-02 4:52 ` Linux v2.5.54 - OHCI-HCD build fails Murray J. Root
2003-01-02 5:00 ` Murray J. Root
2003-01-02 5:16 ` [PATCH] " Andres Salomon
2003-01-02 5:43 ` Murray J. Root
2003-01-02 6:10 ` Andres Salomon
2003-01-02 10:34 ` Linux v2.5.54 SZALAY Attila
2003-01-02 15:50 ` Randy.Dunlap
2003-01-02 15:56 ` Randy.Dunlap
2003-01-03 9:32 ` SZALAY Attila
2003-01-03 11:04 ` SZALAY Attila
2003-01-03 12:19 ` Alan Cox
2003-01-03 12:44 ` Christoph Hellwig
2003-01-03 16:13 ` Randy.Dunlap
2003-01-02 15:08 ` Adrian Bunk
2003-01-02 15:10 ` Christoph Hellwig
2003-01-02 17:18 ` Adrian Bunk
2003-01-02 17:31 ` Jaroslav Kysela
2003-01-02 13:26 ` Adam Belay [this message]
2003-01-03 0:08 ` [2.5.54] OOPS: unable to handle kernel paging request Steven Barnhart
2003-01-03 6:49 ` Paul Rolland
2003-01-02 17:49 ` Linux v2.5.54 Rudmer van Dijk
2003-01-02 23:48 ` [OOPS] Linux v2.5.54 Riva Framebuffer Udo A. Steinberg
2003-01-04 21:13 ` James Simmons
-- strict thread matches above, loose matches on Subject: below --
2003-01-02 14:42 Linux v2.5.54 Paolo Ciarrocchi
2003-01-04 10:20 ` Kasper Dupont
2003-01-04 11:47 Paolo Ciarrocchi
2003-01-04 12:27 ` Kasper Dupont
2003-01-04 14:06 Paolo Ciarrocchi
2003-01-04 14:19 ` Kasper Dupont
2003-01-04 17:10 Paolo Ciarrocchi
2003-01-04 18:14 Paolo Ciarrocchi
2003-01-04 22:14 ` Kasper Dupont
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=20030102132640.GA328@neo.rr.com \
--to=ambx1@neo.rr.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
--cc=zwane@holomorphy.com \
/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