From: Christoph Hellwig <hch@infradead.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
netdev@vger.kernel.org, jonathan@buzzard.org.uk,
tlinux-users@tce.toshiba-dme.co.jp,
Jaroslav Kysela <perex@suse.cz>,
viro@ftp.linux.org.uk
Subject: Re: [RFC: 2.6 patch] remove ISA legacy functions
Date: Sat, 12 Nov 2005 07:12:02 +0000 [thread overview]
Message-ID: <20051112071201.GA29136@infradead.org> (raw)
In-Reply-To: <20051112045216.GY5376@stusta.de>
On Sat, Nov 12, 2005 at 05:52:16AM +0100, Adrian Bunk wrote:
> This patch removes the ISA legacy functions that are deprecated since
> kernel 2.4 and that aren't available on all architectures.
>
> The 7 drivers that were still using this obsolete API are now marked
> as BROKEN.
NACK. Al has patches pending to convert them to proper APIs, please
wait until after that patchseries has landed.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
netdev@vger.kernel.org, jonathan@buzzard.org.uk,
tlinux-users@linux.toshiba-dme.co.jp,
Jaroslav Kysela <perex@suse.cz>,
viro@ftp.linux.org.uk
Subject: Re: [RFC: 2.6 patch] remove ISA legacy functions
Date: Sat, 12 Nov 2005 07:12:02 +0000 [thread overview]
Message-ID: <20051112071201.GA29136@infradead.org> (raw)
In-Reply-To: <20051112045216.GY5376@stusta.de>
On Sat, Nov 12, 2005 at 05:52:16AM +0100, Adrian Bunk wrote:
> This patch removes the ISA legacy functions that are deprecated since
> kernel 2.4 and that aren't available on all architectures.
>
> The 7 drivers that were still using this obsolete API are now marked
> as BROKEN.
NACK. Al has patches pending to convert them to proper APIs, please
wait until after that patchseries has landed.
next prev parent reply other threads:[~2005-11-12 7:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 20:03 [2.6 patch] add -Werror-implicit-function-declaration to CFLAGS Adrian Bunk
2005-11-10 12:28 ` Andrew Morton
2005-11-11 2:12 ` Adrian Bunk
2005-11-11 2:24 ` Andrew Morton
2005-11-11 3:45 ` Randy.Dunlap
2005-11-11 20:18 ` Adrian Bunk
2005-11-11 20:20 ` Adrian Bunk
2005-11-11 20:36 ` Adrian Bunk
2005-11-12 4:52 ` [RFC: 2.6 patch] remove ISA legacy functions Adrian Bunk
2005-11-12 4:52 ` Adrian Bunk
2005-11-12 5:08 ` Jeff Garzik
2005-11-12 5:08 ` Jeff Garzik
2005-11-12 5:11 ` Matthew Wilcox
2005-11-12 5:11 ` Matthew Wilcox
2005-11-12 5:27 ` Jeff Garzik
2005-11-12 5:27 ` Jeff Garzik
2005-11-12 5:29 ` Matthew Wilcox
2005-11-12 5:29 ` Matthew Wilcox
2005-11-12 13:48 ` Al Viro
2005-11-12 13:48 ` Al Viro
2005-11-16 3:56 ` Al Viro
2005-11-16 3:56 ` Al Viro
2005-11-12 7:12 ` Christoph Hellwig [this message]
2005-11-12 7:12 ` Christoph Hellwig
2005-11-12 4:34 ` [2.6 patch] mark virt_to_bus/bus_to_virt as __deprecated on i386 Adrian Bunk
2005-11-11 21:24 ` [2.6 patch] add -Werror-implicit-function-declaration to CFLAGS Andrew Morton
2005-11-11 23:34 ` Sam Ravnborg
2005-11-12 0:33 ` Adrian Bunk
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=20051112071201.GA29136@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=jonathan@buzzard.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=perex@suse.cz \
--cc=tlinux-users@tce.toshiba-dme.co.jp \
--cc=viro@ftp.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.