linux-kernel - Re: pcmcia_ioctl.c compile error

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080429141736.dd483f2b.rdunlap@xenotime.net>
Date:	Tue, 29 Apr 2008 14:17:36 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Russell King <rmk+lkml@....linux.org.uk>
Cc:	Adrian Bunk <bunk@...nel.org>, "Denis V. Lunev" <den@...nvz.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-pcmcia@...ts.infradead.org,
	Alexey Dobriyan <adobriyan@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: pcmcia_ioctl.c compile error

On Tue, 29 Apr 2008 22:14:11 +0100 Russell King wrote:

> On Tue, Apr 29, 2008 at 01:59:02PM -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...
> 
> What don't you get?

Why you said "building new kernels for it".
So it confused me.  It's not strictly a build issue,
it's a run-time issue.


> I've said each time the PCMCIA ioctl removal topic came up that it would
> give me this precise problem.  I've given details of _why_ it would cause
> me that problem.  It's gone ahead inspite of that.


---
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/