mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Christian Dietrich <qy03fugy@stud.informatik.uni-erlangen.de>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	Eric Miao <eric.y.miao@gmail.com>,
	Marek Vasut <marek.vasut@gmail.com>,
	Manuel Lauss <manuel.lauss@gmail.com>,
	Magnus Damm <damm@opensource.se>,
	Karsten Keil <keil@b1-systems.de>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	"Steven A. Falco" <sfalco@harris.com>,
	Russell King <rmk+kernel@arm.linux.org.uk>,
	linux-kernel@vger.kernel.org, linux-pcmcia@lists.infradead.org,
	vamos-dev@i4.informatik.uni-erlangen.de
Subject: Re: [PATCH] Remove dead CONFIG_PCMCIA_IOCTL
Date: Wed, 21 Jul 2010 13:45:26 +0200	[thread overview]
Message-ID: <20100721114526.GA13082@isilmar-3.linta.de> (raw)
In-Reply-To: <20100721113710.GA7724@faui49.informatik.uni-erlangen.de>

Hey,

On Wed, Jul 21, 2010 at 01:37:10PM +0200, Christian Dietrich wrote:
> CONFIG_PCMCIA_IOCTL doesn't exist in Kconfig, therefore removing all
> references for it from the source code. PCMCIA_IOCTL was removed partly
> in a3f916f2c84f2b9e1d32cc0dbfe326a9e380dbfb, but there were a few pieces
> scattered over the source tree, because they are never selected they can
> be removed.

the code is still in there on purpose -- it is only scheduled for removal
for 2.6.36. See Documentation/feature-removal-schedule.txt for details. For
2.6.36, I've already applied a patch to the PCMCIA tree, which you may find
at http://git.kernel.org/?p=linux/kernel/git/brodo/pcmcia-2.6.git;a=summary
(gitweb).

Best,
	Dominik

      reply	other threads:[~2010-07-21 11:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-21 11:37 Christian Dietrich
2010-07-21 11:45 ` Dominik Brodowski [this message]

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=20100721114526.GA13082@isilmar-3.linta.de \
    --to=linux@dominikbrodowski.net \
    --cc=damm@opensource.se \
    --cc=eric.y.miao@gmail.com \
    --cc=keil@b1-systems.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pcmcia@lists.infradead.org \
    --cc=manuel.lauss@gmail.com \
    --cc=marek.vasut@gmail.com \
    --cc=qy03fugy@stud.informatik.uni-erlangen.de \
    --cc=ralf@linux-mips.org \
    --cc=rjw@sisk.pl \
    --cc=rmk+kernel@arm.linux.org.uk \
    --cc=sfalco@harris.com \
    --cc=vamos-dev@i4.informatik.uni-erlangen.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

all inboxes | Powered by JetHome®