From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
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 22:58:45 +0100 [thread overview]
Message-ID: <20080429225845.0f60eb72@core> (raw)
In-Reply-To: <20080429211410.GD31311@flint.arm.linux.org.uk>
> 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.
Which is reasonable.
> 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?
How about delegate some of the control to other people ? There's something
wrong if it has to be you that sorts it out eveyr time - especially as you
effectively manage as many platforms as everyone else put together right
now.
Alan
next prev parent reply other threads:[~2008-04-29 22:06 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
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 [this message]
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=20080429225845.0f60eb72@core \
--to=alan@lxorguk.ukuu.org.uk \
--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