[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180331084150.e6uottdsdagtywbp@mwanda>
Date: Sat, 31 Mar 2018 11:41:50 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Joe Perches <joe@...ches.com>
Cc: Quytelda Kahja <quytelda@...alin.org>, gregkh@...uxfoundation.org,
wsa@...-dreams.de, devel@...verdev.osuosl.org,
driverdev-devel@...uxdriverproject.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 01/75] staging: ks7010: Use the ARRAY_SIZE() macro to
calculate array sizes.
On Fri, Mar 30, 2018 at 11:36:13PM -0700, Joe Perches wrote:
> On Fri, 2018-03-30 at 23:07 -0700, Quytelda Kahja wrote:
> > This macro, provided in 'linux/kernel.h', will calculate the size
> > more succinctly than a division operation.
>
> It's nice that you send patches, but please try to send a
> cover letter with your patch series.
>
There are obviously times when a cover letter is required but what's the
point of that for this particular series? What do you want the cover
letter to say here that isn't obvious to everyone just from glancing at
their inbox?
> Also, 75 patches is quite a lot for a staging patch series.
>
> Please try to send fewer patches in your series, say a
> maximum of 20 or so and see what happens to those patches
> before sending the next set.
Do we really care about that for staging? I can review the first 67
patches basically automatically so they take me about 5 seconds each. I
feel like splitting it up risks introducing more conflicts so it
actually makes the process harder/worse.
regards,
dan carpenter
Powered by blists - more mailing lists