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: <33514b21-25d5-4356-a820-4d2bd11056e9@linaro.org>
Date:   Mon, 23 Oct 2023 10:48:34 +0200
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To:     Linus Walleij <linus.walleij@...aro.org>
Cc:     Andy Gross <agross@...nel.org>,
        Bjorn Andersson <andersson@...nel.org>,
        Konrad Dybcio <konrad.dybcio@...aro.org>,
        linux-arm-msm@...r.kernel.org, linux-gpio@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/2] pinctrl: qcom: lpass-lpi: allow slew rate bit in
 main pin config register

On 23/10/2023 10:27, Linus Walleij wrote:
> On Mon, Oct 23, 2023 at 10:22 AM Krzysztof Kozlowski
> <krzysztof.kozlowski@...aro.org> wrote:
> 
>> On 23/10/2023 10:19, Linus Walleij wrote:
>>> On Fri, Oct 13, 2023 at 4:59 PM Krzysztof Kozlowski
>>> <krzysztof.kozlowski@...aro.org> wrote:
>>>
>>>
>>>> Changes in v2
>>>
>>> I tried to apply this to the pinctrl devel branch:
>>> https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git/log/?h=devel
>>>
>>> It doesn't apply, could you rebase it?
>>
>> The context depends on my previous fix which you applied and sent for
>> v6.6 already:
>> https://lore.kernel.org/linux-arm-msm/CACRpkdaybnYEmkgv7VG4fh5sXQ7uwHm2wH2Khja-P1b6idYr8w@mail.gmail.com/
>>
>> I can rebase, but I am afraid it will cause conflicts. Is it reasonable
>> for you to merge v6.6-rc7 into your devel branch?
> 
> Torvalds is usually not super-happy when we do that, especially
> this late in the development cycle it gets a bit ugly with all
> the stuff that brings in.
> 
> Can we wait with this patch set until the next development
> cycle or is it urgent?

We can wait, no problem with that.

Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ