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: <20080429211410.GD31311@flint.arm.linux.org.uk>
Date:	Tue, 29 Apr 2008 22:14:11 +0100
From:	Russell King <rmk+lkml@....linux.org.uk>
To:	Randy Dunlap <rdunlap@...otime.net>
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, 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?

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.

Concerning the pasic driver.  For fuck sake, why are you bringing that
up.  I made it *perfectly* and *crystal* clear that I *WAS* *NOT* in a
position to fix that thing - BECAUSE I WASN'T GOING TO BE IN FRONT OF A
COMPUTER FOR VERY LONG ON THOSE DAYS.  Which I knew would be the case on
Monday morning.  I _tried_ to stop the thing being merged, but Linus
merged it anyway, and then told me he'd done that _AFTER_ I'd gone to
bed on Monday.  I tried to ensure that I was in a position to cover
_all_ eventualities (except the one which actually occurred.)

So, between Monday midnight and Thursday morning, when do you expect me
to sort the resulting mess out, given that I was not even able to be
in front of a computer until about 10pm on Tuesday and Wednesday?

Oh, maybe you expect me to give up sleeping just for you?

What do you want me to do?  Quit because of it?

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:
--
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/