[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <84B0EA3D-B6D7-4071-AEA6-019B771985B4@antoniou-consulting.com>
Date: Wed, 7 Aug 2013 10:44:22 +0300
From: Pantelis Antoniou <panto@...oniou-consulting.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Tony Lindgren <tony@...mide.com>,
Russell King <linux@....linux.org.uk>,
BenoƮt Coussno <b-cousson@...com>,
Paul Walmsley <paul@...an.com>,
Sourav Poddar <sourav.poddar@...com>,
Russ Dill <Russ.Dill@...com>, Felipe Balbi <balbi@...com>,
Koen Kooi <koen@...cuitco.com>, linux-omap@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5/5] arm: omap: Proper cleanups for omap_device
Hi Greg,
On Aug 6, 2013, at 1:14 PM, Greg Kroah-Hartman wrote:
> On Tue, Aug 06, 2013 at 12:37:25PM +0300, Pantelis Antoniou wrote:
>>> I don't like this at all, sorry.
>>>
>>
[snip]
>> Don't shoot the messenger please...
>>
>> This is all about fixing a crash without messing too many things.
>
> I understand, it's not your fault at all.
Let's start talking about the patchset again.
I know all of this code is rather distasteful but it's only purpose
is to fix a bunch of crashes in a code path that was supposed to be working,
namely the removal of a platform device, in the supposedly well supported
ARM OMAP arch.
Can we agree to at least not crashing until we get to a consensus about
fixing the whole mess properly? This will take at least a few minor
kernel revisions while in the meantime users get crashes everyday.
Regards
-- Pantelis
--
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/
Powered by blists - more mailing lists