Messages in this thread | | | Date | Thu, 20 Aug 2020 10:23:47 -0400 | From | Steven Rostedt <> | Subject | Re: [PATCH v4 3/3] media: atomisp: Only use trace_printk if allowed |
| |
On Thu, 20 Aug 2020 17:14:12 +0800 Nicolas Boichat <drinkcat@chromium.org> wrote:
> Technically, we could only initialize the trace_printk buffers > when the print env is switched, to avoid the build error and > unconditional boot-time warning, but I assume this printing > framework will eventually get removed when the driver moves out > of staging?
Perhaps this should be converting into a trace event. Look at what bpf did for their bpf_trace_printk().
The more I think about it, the less I like this series.
-- Steve
| |