[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080719232256.f0648c27.sfr@canb.auug.org.au>
Date: Sat, 19 Jul 2008 23:22:56 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: "Vegard Nossum" <vegard.nossum@...il.com>
Cc: "Mariusz Kozlowski" <m.kozlowski@...land.pl>,
"Dave Hansen" <haveblue@...ibm.com>,
"Greg Kroah-Hartman" <gregkh@...e.de>,
kernel-testers@...r.kernel.org, linux-next@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>,
"Pekka Enberg" <penberg@...helsinki.fi>
Subject: Re: linux-next: Tree for July 18: warning at kernel/lockdep.c:2068
trace_hardirqs_on_caller
Hi Vegard,
On Sat, 19 Jul 2008 14:59:12 +0200 "Vegard Nossum" <vegard.nossum@...il.com> wrote:
>
> Ehe... and this is the reason why: The code was added by this patch:
>
> commit 0e3638d1e04040121af00195f7e4628078246489
> Author: Dave Hansen <haveblue@...ibm.com>
> Date: Thu Mar 16 17:30:16 2006 -0800
>
> warn when statically-allocated kobjects are used
>
> ..which only exists in -next. Is that just a truly ancient patch, or
> did somebody forget to adjust their clock?
>
> (Stephen: Maybe this has been answered before, but what's the best way
> to figure out where it came from?)
The easiest way is to ask me to look in my source tree (since I have the
heads of all the branches I merge - at least until the next day and gitk
then makes it easy ...).
In this case, that commit comes from the driver-core tree.
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists