From: Dave Young <hidave.darkstar@gmail.com>
To: rostedt@goodmis.org
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
akpm@linux-foundation.org, mm-commits@vger.kernel.org,
gregkh@suse.de, kosaki.motohiro@jp.fujitsu.com,
lizf@cn.fujitsu.com, mingo@elte.hu, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: + kernelh-printk-panic-string-cleanup.patch added to -mm tree
Date: Thu, 25 Feb 2010 09:56:36 +0800 [thread overview]
Message-ID: <a8e1da1002241756x6aa1a2fcqfb42d0fdd6962418@mail.gmail.com> (raw)
In-Reply-To: <1267050119.24271.7820.camel@gandalf.stny.rr.com>
On Thu, Feb 25, 2010 at 6:21 AM, Steven Rostedt <rostedt@goodmis.org> wrote:
> On Wed, 2010-02-24 at 22:34 +0100, Frederic Weisbecker wrote:
>> On Wed, Feb 24, 2010 at 01:07:15PM -0800, akpm@linux-foundation.org wrote:
>> >
>
>> That said, it's probably sane to think about a new header to put
>> these tracing prototypes, if it's included by kernel.h,
>> linux/ftrace.h is already filled with non-general purpose things.
>> So may be linux/trace.h ? Yeah this could be confusing, Steve what
>> do you think?
>>
>> And all in one, it would probably better to split this in three
>> patches: one that moves printk helpers out of kernel.h to printk.h,
>> another following the same pattern for panic things and another one
>> for tracing things.
>
> Yeah, I'm fine with moving the tracing related stuff in kernel.h into a
> trace.h file and keep ftrace.h specific to ftrace in general.
>
> But I still find it necessary that trace.h gets included by kernel.h.
Thanks, will do
>
> I can just imaging Thomas yelling at me more when he adds a
> tracing_off() or trace_printk() somewhere and then gets a warning about
> it not being declared.
>
> I also gave that patch a NAK, in case that carries any weight.
>
> -- Steve
>
>
>
--
Regards
dave
next prev parent reply other threads:[~2010-02-25 1:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201002242107.o1OL7F6v020376@imap1.linux-foundation.org>
2010-02-24 21:34 ` Frederic Weisbecker
2010-02-24 22:21 ` Steven Rostedt
2010-02-25 1:56 ` Dave Young [this message]
2010-02-25 1:55 ` Dave Young
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=a8e1da1002241756x6aa1a2fcqfb42d0fdd6962418@mail.gmail.com \
--to=hidave.darkstar@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=gregkh@suse.de \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=mm-commits@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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®