From: Harvey Harrison <harvey.harrison@gmail.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
Adrian Bunk <bunk@kernel.org>, "Denis V. Lunev" <den@openvz.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-pcmcia@lists.infradead.org,
Alexey Dobriyan <adobriyan@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: pcmcia_ioctl.c compile error
Date: Tue, 29 Apr 2008 14:03:07 -0700 [thread overview]
Message-ID: <1209502988.24729.31.camel@brick> (raw)
In-Reply-To: <20080429135902.504b6362.rdunlap@xenotime.net>
On Tue, 2008-04-29 at 13:59 -0700, Randy Dunlap wrote:
> On Tue, 29 Apr 2008 21:17:04 +0100 Russell King wrote:
>
> > On Tue, Apr 29, 2008 at 09:27:10PM +0300, Adrian Bunk wrote:
> > > Commit 9c37066d888bf6e1b96ad12304971b3ddeabbad0 (proc: remove proc_bus)
> > > came through -mm that contains a patch implementing the overdue removal
> > > of the PCMCIA control ioctl that did not yet make it into Linus' tree:
> >
> > Okay, this means at least one of my platforms is now dead as far as
> > building new kernels for it, and nothing I can do about that. Ho hum.
>
> I don't get it. Several of us had building problems for a few
> days with some pasic driver. We posted some bug reports and
> some patches, but we put up with it for a few days...
>
I believe Russell is referring to the removal of the ioctl, not the
compile breakage.
Harvey
next prev parent reply other threads:[~2008-04-29 21:03 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 [this message]
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
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=1209502988.24729.31.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=den@openvz.org \
--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