From: David Miller <davem@davemloft.net>
To: mingo@elte.hu
Cc: randy.dunlap@oracle.com, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org, akpm@linux-foundation.org,
nhorman@tuxdriver.com, rostedt@goodmis.org
Subject: Re: [PATCH -next] trace_skb: fix build when CONFIG_NET is not enabled
Date: Mon, 17 Aug 2009 15:33:26 -0700 (PDT) [thread overview]
Message-ID: <20090817.153326.69833512.davem@davemloft.net> (raw)
In-Reply-To: <20090817215808.GB15016@elte.hu>
From: Ingo Molnar <mingo@elte.hu>
Date: Mon, 17 Aug 2009 23:58:08 +0200
>> --- linux-next-20090817.orig/kernel/trace/Kconfig
>> +++ linux-next-20090817/kernel/trace/Kconfig
>> @@ -236,6 +236,7 @@ config BOOT_TRACER
>>
>> config SKB_SOURCES_TRACER
>> bool "Trace skb source information"
>> + depends on NET
>> select GENERIC_TRACER
>> help
>> This tracer helps developers/sysadmins correlate skb allocation and
>
> Hm, there's nothing like this in the tracing tree.
>
> Could we please move kernel/trace/* commits to the tracing tree, so
> that it gets adequate testing and review, etc?
This one (like previous networking tracing changes Neil has
made) touched a decent amount of networking code, and thus
we integrated it into net-next-2.6
next prev parent reply other threads:[~2009-08-17 22:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 20:37 [PATCH -next] trace_skb: fix build when CONFIG_NET is not enabled Randy Dunlap
2009-08-17 21:58 ` Ingo Molnar
2009-08-17 22:33 ` David Miller [this message]
2009-08-17 22:47 ` Ingo Molnar
2009-08-17 22:59 ` David Miller
2009-08-17 23:03 ` Ingo Molnar
2009-08-17 23:00 ` Ingo Molnar
2009-08-17 23:00 ` David Miller
2009-08-17 23:06 ` Ingo Molnar
2009-08-18 0:03 ` David Miller
2009-08-18 12:13 ` Ingo Molnar
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=20090817.153326.69833512.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nhorman@tuxdriver.com \
--cc=randy.dunlap@oracle.com \
--cc=rostedt@goodmis.org \
/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