LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Adrian Bunk <bunk@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-pcmcia@lists.infradead.org, linux-kernel@vger.kernel.org,
Dominik Brodowski <linux@brodo.de>
Subject: Re: [2.6 patch] the long overdue pcmcia_ioctl.c removal
Date: Wed, 27 Feb 2008 20:44:07 +0000 [thread overview]
Message-ID: <20080227204407.GA10455@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20080227181303.GB29269@cs181133002.pp.htv.fi>
On Wed, Feb 27, 2008 at 08:13:03PM +0200, Adrian Bunk wrote:
> On Mon, Feb 18, 2008 at 05:01:33AM -0800, Andrew Morton wrote:
> > On Wed, 13 Feb 2008 23:31:15 +0200 Adrian Bunk <bunk@kernel.org> wrote:
> >
> > > pcmcia_ioctl.c was scheduled for removal in 2005, and it has a
> > > deprecation printk() since 2005 (sic).
> > >
> > > This patch contains the long overdue removal and the cleanups that are
> > > now possible.
> >
> > I've had this in -mm for ages, with a note that Dominik had a problem with
> > it. Maybe there are subtleties here, dunno.
>
> This removal has bells and whistles and printk() since 2005...
>
> Dominik, what exactly is the problem why we can't remove it now?
I've objected to it in the past because one of the machines I use
every week requires the ioctls to be able to work - the rootfs is on
a CF card and it uses an initrd to work out - at run time - whether
it's supposed to be running off the CF card or some other internal
memory.
Unfortunately, the project closed down, and I didn't have a chance
(nor the bandwidth) to take a copy of the CVS, which means I've *NO*
possibility to rebuild userspace - which effectively means I can't
change it.
Therefore, removal of the PCMCIA ioctls effectively bars me from
upgrading the kernel on this platform.
There are also other desktop GUI controls which talk to the kernel
PCMCIA subsystem via ioctls - which fall into the same "I can't fix
them" category - some of which are already broken through the removal
of the PCMCIA version reporting IOCTL. Eg, it now thinks there's
always a wireless card plugged in.
TBH I've given up trying to fight this continue "lets remove these
IOCTLs which no one uses" crap. Obviously, _I_ use them.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2008-02-27 20:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 21:31 [2.6 patch] the long overdue pcmcia_ioctl.c removal Adrian Bunk
2008-02-18 13:01 ` Andrew Morton
2008-02-27 18:13 ` Adrian Bunk
2008-02-27 20:44 ` Russell King [this message]
2008-02-28 0:24 ` Peter Stuge
2008-02-28 9:15 ` Russell King
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=20080227204407.GA10455@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=linux@brodo.de \
/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;
as well as URLs for NNTP newsgroup(s).