linux-kernel - Re: [PATCH] ARM: dts: sun7i: Add pinmux settings for LCD0 RGB888 output.

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:   Fri, 16 Mar 2018 17:39:23 +0800
From:   Chen-Yu Tsai <wens@...e.org>
To:     Giulio Benetti <giulio.benetti@...ronovasrl.com>
Cc:     Maxime Ripard <maxime.ripard@...tlin.com>,
        devicetree <devicetree@...r.kernel.org>,
        linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
        linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ARM: dts: sun7i: Add pinmux settings for LCD0 RGB888 output.

On Fri, Mar 16, 2018 at 5:19 PM, Giulio Benetti
<giulio.benetti@...ronovasrl.com> wrote:
> Hi Maxime,
>
> Il 16/03/2018 07:47, Maxime Ripard ha scritto:
>>
>> Hi Giulio,
>>
>> On Thu, Mar 15, 2018 at 02:43:30PM +0100, Giulio Benetti wrote:
>>>
>>> The A20 supports RGB888 with H/V sync from LCD0. Add a pinmux setting
>>> for the needed pins.
>>>
>>> Signed-off-by: Giulio Benetti <giulio.benetti@...ronovasrl.com>
>>
>>
>> Like we discussed last time, we only merge this kind of patches if
>> there's an immediate user.
>
>
> You're right.
> In few time(I hope), I'm going to send dts for Linova1-4_3 and Linova1-7,
> where I use those pins.
> I have also to send 2 patches for 2 new panels for panel-simple.
>
> So I think I have to send 2 displays' patches before.
> And a patchset for the 2 boards and rgb888 pins.
>
> One question: do I have to wait for panels' patches to applied and then send
> patchset for boards dts?
> Or can I send a unique patchset?
> Because as I understand those patches should be applied to 2 different
> repositories, right?

If none of them have been merged yet, it's best to send all of them
as part of the same series, and to all parties involved. That way,
people have the full picture of what you're trying to achieve when
they review your patches. Unless your series is really big.

Maintainers will pick up patches that need to go through their trees.
In general you don't need to do much coordination beyond pointing out
whether the patches are safe to go in independently or there are
dependencies that the maintainers need to be aware of.

ChenYu