From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Vegard Nossum" <vegard.nossum@gmail.com>
Cc: "Mariusz Kozlowski" <m.kozlowski@tuxland.pl>,
"Dave Hansen" <haveblue@us.ibm.com>,
"Greg Kroah-Hartman" <gregkh@suse.de>,
kernel-testers@vger.kernel.org, linux-next@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
"Pekka Enberg" <penberg@cs.helsinki.fi>
Subject: Re: linux-next: Tree for July 18: warning at kernel/lockdep.c:2068 trace_hardirqs_on_caller
Date: Sat, 19 Jul 2008 23:22:56 +1000 [thread overview]
Message-ID: <20080719232256.f0648c27.sfr@canb.auug.org.au> (raw)
In-Reply-To: <19f34abd0807190559y2fe5ebf9h7095793e82de3122@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
Hi Vegard,
On Sat, 19 Jul 2008 14:59:12 +0200 "Vegard Nossum" <vegard.nossum@gmail.com> wrote:
>
> Ehe... and this is the reason why: The code was added by this patch:
>
> commit 0e3638d1e04040121af00195f7e4628078246489
> Author: Dave Hansen <haveblue@us.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@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-07-19 13:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 9:53 linux-next: Tree for July 18 Stephen Rothwell
2008-07-19 7:28 ` linux-next: Tree for July 18: warning at kernel/lockdep.c:2068 trace_hardirqs_on_caller Mariusz Kozlowski
2008-07-19 9:55 ` Vegard Nossum
2008-07-19 12:56 ` Pekka Enberg
2008-07-19 12:59 ` Vegard Nossum
2008-07-19 13:22 ` Stephen Rothwell [this message]
2008-07-19 22:17 ` Greg KH
2008-07-19 22:27 ` Vegard Nossum
2008-07-19 22:41 ` Greg KH
2008-07-19 22:44 ` Vegard Nossum
2008-07-19 22:58 ` Greg KH
2008-07-19 23:11 ` Vegard Nossum
2008-07-19 23:20 ` Greg KH
2008-07-20 12:51 ` Bernhard Walle
2008-07-20 9:01 ` Dave Hansen
2008-07-20 9:35 ` Thomas Meyer
2008-07-20 13:03 ` Bernhard Walle
2008-07-20 15:44 ` Bernhard Walle
2008-07-21 13:17 ` Vivek Goyal
2008-07-21 13:25 ` Bernhard Walle
2008-07-21 13:39 ` Vivek Goyal
2008-07-21 15:00 ` Bernhard Walle
2008-07-22 6:15 ` Yasunori Goto
2008-07-20 12:48 ` Bernhard Walle
2008-07-19 7:39 ` linux-next: Tree for July 18: nfs problems Mariusz Kozlowski
2008-07-19 9:35 ` linux-next: Tree for July 18: powerpc g3 hangs Mariusz Kozlowski
2008-07-19 15:31 ` linux-next: Tree for July 18 (very early crash on x86_32) Bartlomiej Zolnierkiewicz
2008-07-20 0:20 ` linux-next: Tree for July 18: sky2 WOL broken Rafael J. Wysocki
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=20080719232256.f0648c27.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=gregkh@suse.de \
--cc=haveblue@us.ibm.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=m.kozlowski@tuxland.pl \
--cc=penberg@cs.helsinki.fi \
--cc=vegard.nossum@gmail.com \
/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
all inboxes | Powered by JetHome®