From: David Laight <David.Laight@ACULAB.COM>
To: 'Nicolas Boichat' <drinkcat@chromium.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
lkml <linux-kernel@vger.kernel.org>,
"Linux Media Mailing List" <linux-media@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Josh Poimboeuf <jpoimboe@redhat.com>
Subject: RE: [PATCH v4 3/3] media: atomisp: Only use trace_printk if allowed
Date: Fri, 21 Aug 2020 12:18:28 +0000 [thread overview]
Message-ID: <6c5249afad274ce49e643d9b05706e3a@AcuMS.aculab.com> (raw)
In-Reply-To: <CANMq1KDT+uecuqxXRsxv9-sMv0sGXk6ZQ3hWv0aK34dfzaJXyg@mail.gmail.com>
From: Nicolas Boichat
> Sent: 21 August 2020 13:07
...
> > You might also want a #define that can set temporarily
> > to enable traces in a specific file/module even though
> > CONFIG_TRACE=n.
>
> I don't understand how traces are supposed to work with CONFIG_TRACE=n?
Probably because I meant something different :-)
You want the kernel built so that there are no (expanded)
calls to trace_printf() but with support for modules that
contain them.
Then I can load a module into a distro kernel that
contains trace_printf() calls for debug testing.
Which is why I was suggesting a config option that
only rand-config builds would ever set that would
cause the calls to generate compile-time errors.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2020-08-21 12:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 9:14 [PATCH v4 1/3, RESEND] media: camss: vfe: Use trace_printk for debugging only Nicolas Boichat
2020-08-20 9:14 ` [PATCH v4 3/3] media: atomisp: Only use trace_printk if allowed Nicolas Boichat
2020-08-20 14:23 ` Steven Rostedt
2020-08-21 0:13 ` Nicolas Boichat
2020-08-21 0:36 ` Steven Rostedt
2020-08-21 1:39 ` Nicolas Boichat
2020-08-21 1:57 ` Steven Rostedt
2020-08-21 2:36 ` Joe Perches
2020-08-21 2:42 ` Nicolas Boichat
2020-08-21 2:49 ` Joe Perches
2020-08-21 3:04 ` Steven Rostedt
2020-08-21 3:08 ` Steven Rostedt
2020-08-21 2:44 ` Steven Rostedt
2020-08-21 2:39 ` Nicolas Boichat
2020-08-21 3:01 ` Steven Rostedt
2020-08-21 12:19 ` Nicolas Boichat
2020-08-21 8:48 ` David Laight
2020-08-21 10:27 ` Nicolas Boichat
2020-08-21 11:32 ` David Laight
2020-08-21 12:07 ` Nicolas Boichat
2020-08-21 12:18 ` David Laight [this message]
2020-08-21 12:37 ` Nicolas Boichat
2020-08-20 14:21 ` [PATCH v4 1/3, RESEND] media: camss: vfe: Use trace_printk for debugging only Steven Rostedt
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=6c5249afad274ce49e643d9b05706e3a@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=drinkcat@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sakari.ailus@linux.intel.com \
--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;
as well as URLs for NNTP newsgroup(s).