public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski.net>
To: rmk@arm.linux.org.uk
Cc: linux-pcmcia@lists.infradead.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,
	Vincent Sanders <vince@kyllikki.org>
Subject: Re: [PATCH 5/5] pcmcia: disable pcmcia ioctl for !ARM, prepare for removal
Date: Sat, 15 May 2010 16:55:58 +0200	[thread overview]
Message-ID: <20100515145558.GA3184@comet.dominikbrodowski.net> (raw)
In-Reply-To: <20100515144639.GA10987@flint.arm.linux.org.uk>

Russell,

On Sat, May 15, 2010 at 03:46:39PM +0100, Russell King wrote:
> On Sat, May 15, 2010 at 04:37:05PM +0200, Dominik Brodowski wrote:
> > Russell,
> > 
> > On Sat, May 15, 2010 at 03:24:10PM +0100, Russell King wrote:
> > > On Wed, Mar 03, 2010 at 09:00:48AM +0100, Dominik Brodowski wrote:
> > > > Furthermore, the last legitimate use of the ioctl to be reported
> > > > relates to the ARM architecture in 2008.[1] Attempts to resolve
> > > > this issue turned out unsuccessful so far.[2] Other usages have only
> > > > been reported as hear-say. If there are any legitiate and necessary
> > > > use-cases remaining, please speak out before the end of the grace
> > > > period until 2.6.3{5,6}(-rc1).
> > > 
> > > What's the point of speaking out?  You don't take any notice of people
> > > who do, and you continue your crusade of wanting to remove it.  Please,
> > > stop giving the impression that you give a damn of what people say about
> > > the ioctl interface.
> > 
> > The _only_ person who really has spoken out is you. All my requests to
> > actually see source code or actual use cases (e.g. which parts of the ioctl
> > do actually get called) did not lead to _anything_.
> 
> See the source code?  You clearly haven't been reading what I've been
> saying to you on the subject if you think I can produce source code.
> I've already explained this to you several times, but it seems to be
> constantly ignored.

That's why there is the _other_ alternative: "actual use cases (e.g. which
parts of the ioctl do actually get called)". For this, you only need to be
able to update/modify the kernel. More than two years ago, you signalised
to do exactly this:

| I'll spend some time this coming weekend working out precisely what it
| requires from the ioctl interface - maybe we can have a cut-down ioctl
| interface that bolts straight on as an "add on" to the new controls
| without being too invasive, while still allowing its PCMCIA bits to
| work.

[ http://lists.infradead.org/pipermail/linux-pcmcia/2008-April/005450.html ]

I haven't heard anything about the result of this experiment, even though
asking a number of times (e.g.
http://lists.infradead.org/pipermail/linux-pcmcia/2010-January/006740.html ).

Best,
	Dominik

  reply	other threads:[~2010-05-15 14:56 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 [this message]
2010-03-03  8:30 ` [git pull] more PCMCIA updates for 2.6.34 (including ioctl deprecation) Russell King
2010-03-03  8:43   ` 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=20100515145558.GA3184@comet.dominikbrodowski.net \
    --to=linux@dominikbrodowski.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jaswinder@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pcmcia@lists.infradead.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=rpjday@crashcourse.ca \
    --cc=vince@kyllikki.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox