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: <14413b20-e8d7-ccf7-172c-0238bfa51c68@quicinc.com>
Date:   Tue, 4 Oct 2022 11:05:45 -0500
From:   Melody Olvera <quic_molvera@...cinc.com>
To:     Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
        Andy Gross <agross@...nel.org>,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        Stephen Boyd <sboyd@...nel.org>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Ulf Hansson <ulf.hansson@...aro.org>
CC:     Bhupesh Sharma <bhupesh.sharma@...aro.org>,
        <linux-arm-msm@...r.kernel.org>, <linux-mmc@...r.kernel.org>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/5] Add misc support for QDU1000/QRU1000 SoCs



On 10/4/2022 10:27 AM, Melody Olvera wrote:
> On 10/1/2022 4:34 AM, Krzysztof Kozlowski wrote:
>> On 01/10/2022 05:06, Melody Olvera wrote:
>>> This series firmware, SoC, rpmpd, tz-log, and mmc bindings as well as
>>> pmic, rpmpd, and socinfo support for QDU1000 and QRU1000 SoCs.
>>>
>>> This patchset is based off of [1] and [2] YAML conversion patches.
>> All of your patchsets were sent to wrong Bjorn's address. This means
>> either you based on mainline (which is reasonable but for some reason
>> address was not fixed in mainline...) or on some older linux-next.
>>
>> I propose to rebase on recent linux-next, so you will get proper Bjorn's
>> email.
>>
>> Best regards,
>> Krzysztof
> Thanks Krzysztof. Yeah I figured that out; will add his most recent
> email in the next patchset. I was working on the tip of the linux-next
> stable branch, but does it make more sense to rebase on the master
> branch of linux-next prior to submitting? 
> Thanks, Melody 

Fixed formatting.

















Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ