Em Fri, 14 Oct 2016 20:22:40 +0200 SF Markus Elfring <[email protected]> escreveu:
> > diff --git a/drivers/media/dvb-core/dmxdev.c > > b/drivers/media/dvb-core/dmxdev.c > > index 7b67e1dd97fd..1e96a6f1b6f0 100644 > > --- a/drivers/media/dvb-core/dmxdev.c > > +++ b/drivers/media/dvb-core/dmxdev.c > > @@ -20,6 +20,8 @@ > > * > > */ > > > > +#define pr_fmt(fmt) "dmxdev: " fmt > > + > > #include <linux/sched.h> > > #include <linux/spinlock.h> > > #include <linux/slab.h> > > How do you think to use an approach like the following there? > > > +#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt > > > or eventually > > > +#define MY_LOG_PREFIX KBUILD_MODNAME ": " > +#define pr_fmt(fmt) MY_LOG_PREFIX fmt we use a lot KBUILD_MODNAME on driver's pr_fmt() macros. However, in this specific case, it is not a good idea, as this patch is touching at the DVB core, with is composed by several different and almost independent parts. So, we want to know what part of the DVB core is producing such messages. Regards, Mauro -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
