[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210813100536.xkjzfq5pstbhdwru@viti.kaiser.cx>
Date: Fri, 13 Aug 2021 12:05:36 +0200
From: Martin Kaiser <martin@...ser.cx>
To: Dan Carpenter <dan.carpenter@...cle.com>
Cc: Phillip Potter <phil@...lpotter.co.uk>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Larry Finger <Larry.Finger@...inger.net>,
Michael Straube <straube.linux@...il.com>,
linux-staging@...ts.linux.dev,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 3/5] staging: r8188eu: (trivial) remove a duplicate debug
print
Hi Dan and Phil,
Thus wrote Dan Carpenter (dan.carpenter@...cle.com):
> Please think of the subject and the commit message as two different
> things. Often it's people reviewing on email will only read one or the
> other. In other words just restate the subject:
ok, I'll keep that in mind for further patches.
> > Dear Martin,
> > Just my personal opinion, but I'd be inclined to strip out all DBG_88E
> > calls totally. If there are necessary functions being called such as
> > device_may_wakeup() we can always just keep this part and remove the
> > macro call (not checked this function out myself yet). Thanks.
I'd agree with you, Phil. Most DBG_88E prints don't say anything useful.
This comment from Greg made me drop the DBG_88E removal for now
https://lore.kernel.org/linux-staging/20210803201511.29000-1-martin@kaiser.cx/T/#m05d82a0ca8ed36180ebdc987114b4d892445c52d
A compromise would be to remove only those DBG_88E prints which are
really not helpful.
Best regards,
Martin
Powered by blists - more mailing lists