From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263537AbTLURI7 (ORCPT ); Sun, 21 Dec 2003 12:08:59 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263618AbTLURI7 (ORCPT ); Sun, 21 Dec 2003 12:08:59 -0500 Received: from astound-64-85-224-253.ca.astound.net ([64.85.224.253]:25092 "EHLO master.linux-ide.org") by vger.kernel.org with ESMTP id S263537AbTLURI5 (ORCPT ); Sun, 21 Dec 2003 12:08:57 -0500 Date: Sun, 21 Dec 2003 09:08:43 -0800 (PST) From: Andre Hedrick To: Jamie Lokier cc: linux-kernel@vger.kernel.org Subject: Re: Linux Device Drivers 3rd Edition In-Reply-To: <20031221110630.GD3438@mail.shareable.org> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Gee Jamie: Maybe if you would or could read past comments in the thread, you'd catch a clue, but let me quote myself from a few days back. "Point, the API is being documented, sometimes not as timely as desired." Clearly this acknowledges the API is a snapshot in time which is published. My past experience (now discounted by all) has observed, Linus does not change, tries very hard to avoid changing, the kernel API during a kernel series minor revsion number. I think I will use one of my favorite viro quotes that I gotten many times over the years. "Sod Off!" Cheers, Andre Hedrick LAD Storage Consulting Group On Sun, 21 Dec 2003, Jamie Lokier wrote: > Andre Hedrick wrote: > > So this is the third release to publish the documented API to the writing > > kernel level device drivers? > > I guess not: it's a guide (a good one), but not an exact reference, > due to the fact that the API changes from version to version, and that > the kernel API is not required to match the documentation. > > -- Jamie >