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] [day] [month] [year] [list]
Message-ID: <CAD=FV=WXGGHTAgH7O6MP3eOp4HLAwkBAOJ9L63ow3PSdkUtCYg@mail.gmail.com>
Date:   Thu, 20 Oct 2022 15:36:20 -0700
From:   Doug Anderson <dianders@...omium.org>
To:     Bjorn Andersson <andersson@...nel.org>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        yunlong.jia@....corp-partner.google.com, henrysun@...gle.com,
        devicetree@...r.kernel.org, moragues@...omium.org,
        agross@...nel.org, robh+dt@...nel.org,
        linux-arm-msm@...r.kernel.org,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Konrad Dybcio <konrad.dybcio@...ainline.org>
Subject: Re: (subset) [PATCH v3 1/2] dt-bindings: arm: qcom: Document
 additional skus for sc7180 pazquel360

Hi,

On Mon, Oct 17, 2022 at 8:15 PM Bjorn Andersson <andersson@...nel.org> wrote:
>
> On Thu, 1 Sep 2022 02:49:57 +0000, Yunlong Jia wrote:
> > pazquel360 is an extension project based on pazquel.
> > We create 3 sku on pazquel360:
> >    sku 20 for LTE with physical SIM _and_ eSIM and WiFi
> >    sku 21 for WiFi only
> >    sku 22 for LTE with only a physical SIM
> >  Both sku20 and sku22 are LTE SKUs.
> >  One has the eSIM stuffed and one doesn't.
> >  There is a single shared device tree for the two.
> >
> > [...]
>
> Applied, thanks!
>
> [1/2] dt-bindings: arm: qcom: Document additional skus for sc7180 pazquel360
>       commit: 185d192d0a7b565a24b3f7456a2f84f169ab087a
> [2/2] arm64: dts: qcom: Add sc7180-pazquel360
>       commit: 2f72a4f54cdb4fd0ebea9a2dea65756d3e676be2

FWIW, it looks like you landed v3 instead of v5. See:

https://lore.kernel.org/r/20220923083657.v5.3.Iea2d2918adfff2825b87d428b5732717425c196f@changeid/

Presumably something about your process got confused because Yunlong
changed the email address they were sending it from (I think someone
requested not to use an "corp-partner" email address).

The other difference between v3 and v5 is the touchscreen. Presumably
Yunlong can send a followup patch to add the touchscreen atop what
you've landed.

-Doug

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ