public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: rdunlap@xenotime.net, harvey.harrison@gmail.com, bunk@kernel.org,
	den@openvz.org, linux-pcmcia@lists.infradead.org,
	adobriyan@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: pcmcia_ioctl.c compile error
Date: Tue, 29 Apr 2008 15:12:33 -0700	[thread overview]
Message-ID: <20080429151233.401a9330.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080429215620.GA14848@flint.arm.linux.org.uk>

On Tue, 29 Apr 2008 22:56:20 +0100
Russell King <rmk+lkml@arm.linux.org.uk> wrote:

> On Tue, Apr 29, 2008 at 02:38:24PM -0700, Andrew Morton wrote:
> > On Tue, 29 Apr 2008 14:15:20 -0700
> > Randy Dunlap <rdunlap@xenotime.net> wrote:
> > 
> > > > > I believe Russell is referring to the removal of the ioctl, not the
> > > > > compile breakage.
> > > > > 
> > > > 
> > > > That would be interesting information (although I have a vague feeling that
> > > > it has been discussed before).
> > > 
> > > Yes:  http://lkml.org/lkml/2008/2/27/291
> > > (now that Harvey reminded me/us)
> > 
> > oh, OK, whatever, that's easy.  I dropped the old patch and queued this
> > one:
> 
> 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.

umm, well,

a) as your machine still needed the ioctl code, we can assume that there
   are others out there.  So it's unclear that we _can_ delete it, or change
   its interfaces.

b) the rate of change in that code is very close to zero.  I'd say just let
   it be.  It's not a good use of one's time?


  reply	other threads:[~2008-04-29 22:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-29 18:27 pcmcia_ioctl.c compile error Adrian Bunk
2008-04-29 18:38 ` Andrew Morton
2008-04-29 20:17 ` Russell King
2008-04-29 20:59   ` Randy Dunlap
2008-04-29 21:03     ` Harvey Harrison
2008-04-29 21:07       ` Randy Dunlap
2008-04-29 21:09       ` Andrew Morton
2008-04-29 21:15         ` Randy Dunlap
2008-04-29 21:38           ` Andrew Morton
2008-04-29 21:56             ` Russell King
2008-04-29 22:12               ` Andrew Morton [this message]
2008-04-29 22:04         ` Alan Cox
2008-04-29 21:14     ` Russell King
2008-04-29 21:17       ` Randy Dunlap
2008-04-29 21:58       ` Alan Cox
2008-04-29 22:35         ` 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=20080429151233.401a9330.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=adobriyan@gmail.com \
    --cc=bunk@kernel.org \
    --cc=den@openvz.org \
    --cc=harvey.harrison@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pcmcia@lists.infradead.org \
    --cc=rdunlap@xenotime.net \
    --cc=rmk+lkml@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox