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:   Wed, 12 Jul 2017 10:38:38 +0800
From:   Chen-Yu Tsai <wens@...e.org>
To:     Maxime Ripard <maxime.ripard@...e-electrons.com>
Cc:     Chen-Yu Tsai <wens@...e.org>, David Airlie <airlied@...ux.ie>,
        Mark Rutland <mark.rutland@....com>,
        dri-devel <dri-devel@...ts.freedesktop.org>,
        devicetree <devicetree@...r.kernel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Rob Herring <robh@...nel.org>
Subject: Re: [PATCH] dt-bindings: display: sunxi: Improve endpoint ID scheme readability

On Wed, Jul 12, 2017 at 3:31 AM, Maxime Ripard
<maxime.ripard@...e-electrons.com> wrote:
> On Mon, Jul 10, 2017 at 11:48:00PM +0800, Chen-Yu Tsai wrote:
>> On Sun, Jun 18, 2017 at 10:05 PM, Rob Herring <robh@...nel.org> wrote:
>> > On Wed, Jun 14, 2017 at 02:30:16PM +0800, Chen-Yu Tsai wrote:
>> >> The explanation for the endpoint ID numbering scheme is convoluted
>> >> and hard to understand.
>> >>
>> >> This patch aims to improve the readability of it by combining the
>> >> existing two paragraphs, while also providing a diagram example,
>> >> and how endpoints should be numbered based on that example.
>> >>
>> >> Signed-off-by: Chen-Yu Tsai <wens@...e.org>
>> >> ---
>> >>
>> >> Hope this helps. I'm not sure I can improve this even more without
>> >> spelling out all cases.
>> >>
>> >> ---
>> >>  .../bindings/display/sunxi/sun4i-drm.txt           | 36 ++++++++++++++++------
>> >>  1 file changed, 27 insertions(+), 9 deletions(-)
>> >
>> > Acked-by: Rob Herring <robh@...nel.org>
>>
>> Maxime, this patch seems to have fallen through the cracks.
>>
>> Could you queue it as a fix for 4.13?
>
> Sorry, I don't know why I overlooked it.
>
> Is it really 4.13 material though? It doesn't look that urgent.

Unless I'm mistaken, this clarifies the numbering scheme introduced
in 4.13. I'd say that's enough reason to have it in the same release.

But I should update the diagram first. The backend <-> TCON mux is
missing. And maybe a Fixes tag.

ChenYu

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ