linux-kernel - Re: [PATCH V2 1/3] mfd: wm8994-core: don't split lines unnecessarily

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20161005084911.GG29257@dell>
Date:   Wed, 5 Oct 2016 09:49:11 +0100
From:   Lee Jones <lee.jones@...aro.org>
To:     Viresh Kumar <viresh.kumar@...aro.org>
Cc:     linaro-kernel@...ts.linaro.org, Mark Brown <broonie@...nel.org>,
        Krzysztof Kozłowski <k.kozlowski@...sung.com>,
        Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>,
        patches@...nsource.wolfsonmicro.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2 1/3] mfd: wm8994-core: don't split lines unnecessarily

On Wed, 05 Oct 2016, Viresh Kumar wrote:

> On 04-10-16, 15:41, Lee Jones wrote:
> > On Mon, 03 Oct 2016, Viresh Kumar wrote:
> > 
> > > On 16-09-16, 08:56, Viresh Kumar wrote:
> > > > These can fit in a single line (80 columns), don't split lines
> > > > unnecessarily.
> > > > 
> > > > Signed-off-by: Viresh Kumar <viresh.kumar@...aro.org>
> > > > 
> > > > ---
> > > > V1->V2: New patch
> > > > ---
> > > >  drivers/mfd/wm8994-core.c | 6 ++----
> > > >  1 file changed, 2 insertions(+), 4 deletions(-)
> > > 
> > > Ping!!
> > 
> > Don't do that!
> 
> Okay, but what's exactly wrong with that? Its been 20 days that I have
> heard anything from you on this. Pinging the maintainers is the only
> option other people have, right?

You are experienced enough to know better than this.

a) Contentless pings have never been acceptable.  If you genuinely
think a patch has been forgotten you should resubmit with a
[RESEND]. That is their entire purpose.

b) You submitted this patch right at the end of the release cycle, and
your ping was sent during the merge-window.  Most Maintainers, myself
included, like to have patches soak tested in -next for at least a
couple of weeks prior to acceptance.

c) The merge-window is open.  We are likely conducting final tests and
formatting pull-requests during this time.  As an experienced
submitter, I would have expected you to follow the release cycle and
know that sending patches late is cause for delay.

d) Maintainers take vacations and attend conferences, so some delays
are to be expected.

FYI: Your patch has not slipped through the net.  It is in the pile to
be reviewed.  Please be more patient, especially around merge time.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog