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: <3adf74ea-3aba-ad93-977a-8b42ab653ee9@gmail.com>
Date:   Fri, 26 Jun 2020 16:23:14 +0300
From:   Dmitry Osipenko <digetx@...il.com>
To:     Hans Verkuil <hverkuil@...all.nl>,
        Thierry Reding <thierry.reding@...il.com>,
        Jonathan Hunter <jonathanh@...dia.com>,
        Mauro Carvalho Chehab <mchehab@...nel.org>
Cc:     linux-media@...r.kernel.org, linux-tegra@...r.kernel.org,
        devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/4] Tegra Video Decoder driver power management
 corrections

26.06.2020 09:58, Hans Verkuil пишет:
> On 26/06/2020 02:17, Dmitry Osipenko wrote:
>> 24.06.2020 18:23, Dmitry Osipenko пишет:
>>> 24.06.2020 18:16, Hans Verkuil пишет:
>>>> On 24/06/2020 17:08, Dmitry Osipenko wrote:
>>>>> Hello,
>>>>>
>>>>> This small series addresses a Runtime PM issue that was discovered during
>>>>> of Tegra VI driver reviewing by balancing RPM usage count on RPM resume
>>>>> failure. Secondly it fixes reboot on some Tegra devices due to bootloader
>>>>> expecting VDE power partition to be ON at the boot time, which wasn't
>>>>> happening in case of a warm re-booting (i.e. by PMC resetting).
>>>>
>>>> Can you rebase this on top of the media_tree master branch? I think a variant
>>>> of patch 1 has already been applied. I found a mail today where you mentioned
>>>> that you preferred your version (it looks like I missed that) so you'll need to
>>>> rework patch 1.
>>>
>>> Hello Hans,
>>>
>>> I'll take a look at what patches has been applied, my bad for sending
>>> the v2 too late. Thank you for the heads up!
>>>
>>
>> I tested the already-applied variant of the patch 1 and it has the same
>> behaviour as my variant, so it's okay.
>>
>> Would you want me to send a v3 without the conflicting patch 1 or you
>> could apply the patches 2-4 from this series?
>>
> 
> I'll mark 1/4 as superseded and will apply patches 2-4. No need for you
> to do anything.

Thank you!

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ