Messages in this thread | | | Date | Wed, 12 Apr 2023 17:15:01 -0700 | From | Brian Norris <> | Subject | Re: [PATCH] driver core: Don't require dynamic_debug for initcall_debug probe timing |
| |
On Wed, Apr 12, 2023 at 03:58:42PM -0700, Stephen Boyd wrote: > Don't require the use of dynamic debug (or modification of the kernel to > add a #define DEBUG to the top of this file) to get the printk message > about driver probe timing. This printk is only emitted when > initcall_debug is enabled on the kernel commandline, and it isn't > immediately obvious that you have to do something else to debug boot > timing issues related to driver probe. Add a comment too so it doesn't > get converted back to pr_debug(). > > Fixes: eb7fbc9fb118 ("driver core: Add missing '\n' in log messages") > Cc: Christophe JAILLET <christophe.jaillet@wanadoo.fr> > Cc: Brian Norris <briannorris@chromium.org> > Signed-off-by: Stephen Boyd <swboyd@chromium.org> > --- > drivers/base/dd.c | 7 ++++++- > 1 file changed, 6 insertions(+), 1 deletion(-)
Reviewed-by: Brian Norris <briannorris@chromium.org>
| |