From: Russell King <rmk+lkml@arm.linux.org.uk>
To: torvalds@osdl.org, akpm@osdl.org,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
"Robert P. J. Day" <rpjday@crashcourse.ca>,
Jaswinder Singh Rajput <jaswinder@kernel.org>,
linux-kernel@vger.kernel.org, linux-pcmcia@lists.infradead.org
Subject: Re: [git pull] more PCMCIA updates for 2.6.34 (including ioctl deprecation)
Date: Wed, 3 Mar 2010 08:30:11 +0000 [thread overview]
Message-ID: <20100303083010.GA22928@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20100303075944.GA23354@comet.dominikbrodowski.net>
On Wed, Mar 03, 2010 at 08:59:44AM +0100, Dominik Brodowski wrote:
> Please pull from that location insofar as you agree to continue with the
> deprecation of the PCMCIA ioctl. Otherwise, I can prepare a branch
> _without_ this controversial patch to pull from.
So you believe that disabling the button in the graphical environment
to allow PCMCIA cards to be removed (such as CF cards) - leaving the
user to merely pull out the CF card, while the FS is mounted, is a
good idea?
Sounds to me like a data loss scenario.
User APIs changing always breaks stuff.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2010-03-03 8:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 7:59 [git pull] more PCMCIA updates for 2.6.34 (including ioctl deprecation) Dominik Brodowski
2010-03-03 8:00 ` [PATCH 5/5] pcmcia: disable pcmcia ioctl for !ARM, prepare for removal Dominik Brodowski
2010-05-15 14:24 ` Russell King
2010-05-15 14:37 ` Dominik Brodowski
2010-05-15 14:46 ` Russell King
2010-05-15 14:55 ` Dominik Brodowski
2010-03-03 8:30 ` Russell King [this message]
2010-03-03 8:43 ` [git pull] more PCMCIA updates for 2.6.34 (including ioctl deprecation) Dominik Brodowski
2010-03-05 12:07 ` Alan Cox
2010-03-05 12:57 ` Wolfram Sang
2010-03-05 21:41 ` Russell King
2010-03-06 2:44 ` Peter Stuge
2010-03-10 20:45 ` Pavel Machek
2010-03-10 21:00 ` Dominik Brodowski
2010-03-13 6:52 ` Pavel Machek
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=20100303083010.GA22928@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=rpjday@crashcourse.ca \
--cc=torvalds@osdl.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 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.