[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7120836b08b680d54c15fd89b8630ccc67a53116.camel@perches.com>
Date: Sat, 03 Apr 2021 09:17:37 -0700
From: Joe Perches <joe@...ches.com>
To: Fabio Aiuto <fabioaiuto83@...il.com>, gregkh@...uxfoundation.org
Cc: dan.carpenter@...cle.com, linux-staging@...ts.linux.dev,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 00/30] staging: rtl8723bs: remove RT_TRACE logs in
core/*
On Sat, 2021-04-03 at 17:21 +0200, Fabio Aiuto wrote:
> On Sat, Apr 03, 2021 at 08:02:25AM -0700, Joe Perches wrote:
> > On Sat, 2021-04-03 at 11:13 +0200, Fabio Aiuto wrote:
> > > This patchset removes all RT_TRACE usages in core/ files.
> >
> > and hal and include and os_dep
>
> Hi,
>
> I was just about to send the second patchset relative to hal/ files.
> The whole has been split up in directories in order to reduce the
> number of patch per patchset
> It's a good idea, but the patches relative to RT_TRACE removal
> could be huge
That's really not a significant issue.
Simplicity in review is also important.
Mechanization of patch creation can reduce review efforts.
Few people are actively working on this particular codebase.
As far as I can tell no logical defect is being corrected here.
None of this is likely to be backported.
Applying each individual patch has a 'cost' in maintainer time
and review effort.
Fewer patches create lower overall costs.
Good luck...
Powered by blists - more mailing lists