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]
Date:   Thu, 3 Aug 2017 10:26:52 +0200
From:   Peter Rosin <peda@...ntia.se>
To:     Baolin Wang <baolin.wang@...aro.org>, wsa@...-dreams.de,
        Mark Rutland <mark.rutland@....com>,
        Rob Herring <robh+dt@...nel.org>,
        andriy.shevchenko@...ux.intel.com, linux-i2c@...r.kernel.org,
        devicetree@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
        Mark Brown <broonie@...nel.org>,
        wsa+renesas@...g-engineering.com
Subject: Re: [RESEND PATCH v4 1/2] dt-bindings: i2c: Add Spreadtrum I2C
 controller documentation

On 2017-08-03 09:29, Baolin Wang wrote:
> Hi Wolfram,
> 
> On 27 July 2017 at 17:29, Baolin Wang <baolin.wang@...aro.org> wrote:
>> Hi Wolfram,
>>
>> On 24 July 2017 at 14:51, Baolin Wang <baolin.wang@...eadtrum.com> wrote:
>>> Hi Wolfram,
>>>
>>> On 五,  7月 14, 2017 at 05:01:10下午 +0800, Baolin Wang wrote:
>>>> This patch adds the binding documentation for Spreadtrum I2C
>>>> controller device.
>>>>
>>>> Signed-off-by: Baolin Wang <baolin.wang@...eadtrum.com>
>>>> Acked-by: Rob Herring <robh@...nel.org>
>>>> ---
>>>> Changes since v3:
>>>>  - Add Ack from RobH.
>>>>
>>>> Changes since v2:
>>>>  - Change compatible strings to be SoC specific.
>>>>
>>>> Changes since v1:
>>>>  - No updates.
>>>> ---
>>>
>>> Could you apply this patchset if there are no other comments?
>>> It is a long time since the v4 was send out. Thanks.
>>
>> Ping?
> 
> Since this patchset has waited for a long time, could you pick up this
> patchset into your branch? Thanks.

Please calm down. You first sent v4 4 weeks ago in the beginning of the
merge window when everybody are supposedly looking at the integration of
the work from the previous cycle. You have managed to send remainders
four times in those few weeks.

Four weeks is not a "long time", and it's not like you didn't get any
feedback. Part of that feedback was that there was room for improvement.
Have you looked into that? Or have you been busy sending pings? I'm sure
Wolfram will pick the series in time for the next merge window if he's
happy with it, there was that thing about room for improvement...

Cheers,
Peter

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ