Re: [PATCH v18 02/10] dt-bindings: arm: mediatek: mmsys: add mt8195 SoC binding

Re: [PATCH v18 02/10] dt-bindings: arm: mediatek: mmsys: add mt8195 SoC binding

[Jason-JH Lin]

Hello Rob, Krzysztof,

I found the dt-binding patches in this series never appeared in
devicetree-bindings patchwork and trigger the dt-binding check bot.

Do you know the reason for this?
Could you help me with this and let me know what should I do to solve
this problem?

Thanks.

Regards,
Jason-JH.Lin

Re: [PATCH v18 08/10] soc: mediatek: add DDP_DOMPONENT_DITHER0 enum for mt8195 vdosys0

[Jason-JH Lin]

Hi Rex,

Thank for the reviews.

On Fri, 2022-04-15 at 14:24 +0800, Rex-BC Chen wrote:
> On Tue, 2022-04-12 at 18:31 +0800, jason-jh.lin wrote:
> > The mmsys routing table of mt8195 vdosys0 has 2 DITHER components,
> > so mmsys need to add DDP_COMPONENT_DITHER1 and change all usages of
> > DITHER enum form DDP_COMPONENT_DITHER to DDP_COMPONENT_DITHER0.
> > 
> > But its header need to keep DDP_COMPONENT_DITHER enum
> > until drm/mediatek also changed it.
> 
> Hello Jason,
> 
> IMO, it's strange.
> In this case , I think you sholud squash [v18,08/10] and [v18,09/10].
> Therefore, you don't need to describe this here.
> 

As the CK reply before:

https://patchwork.kernel.org/project/linux-mediatek/patch/20220407030409.9664-4-jason-jh.lin@mediatek.com/#24806029

[v18,08/10] and [v18,09/10] belong to 2 different trees, so I add the
description here.

Regards,
Jason-JH.Lin


> BRs,
> Rex
> 
-- 
Jason-JH Lin <jason-jh.lin@mediatek.com>

Re: [PATCH v18 02/10] dt-bindings: arm: mediatek: mmsys: add mt8195 SoC binding

[Krzysztof Kozlowski]

[-- Attachment #1: Type: text/plain, Size: 940 bytes --]

On 14/04/2022 05:11, Jason-JH Lin wrote:
> Hello Rob, Krzysztof,
> 
> I found the dt-binding patches in this series never appeared in
> devicetree-bindings patchwork and trigger the dt-binding check bot.
> 
> Do you know the reason for this?
> Could you help me with this and let me know what should I do to solve
> this problem?

Hi,

All your emails end up regularly in my Gmail spam folder, similarly to
emails from some other Mediatek people (e.g. Rex-BC Chen), so maybe
that's the cause?

Why they end up in spam? I don't know, but it would be nice if you could
work on this with your IT department. I know that corporate environments
are tricky to change, but there is not much else to do. Google flags
your emails always as spam.

You can see in the headers two DMARC failures:
dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=QUARANTINE)
header.from=mediatek.com

Spamming 27 recipients is maybe another reason...

Best regards,
Krzysztof

[-- Attachment #2: mediatek-spam.txt --]
[-- Type: text/plain, Size: 1501 bytes --]

smtp.mailfrom="SRS0=SiiB=UW=mediatek.com=jason-jh.lin@kernel.org";
       dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=QUARANTINE) header.from=mediatek.com
Return-Path: <SRS0=SiiB=UW=mediatek.com=jason-jh.lin@kernel.org>
Received: from ams.source.kernel.org (ams.source.kernel.org. [2604:1380:4601:e00::1])
        by mx.google.com with ESMTPS id m2-20020a17090679c200b006e881149e83si5514956ejo.629.2022.04.12.03.31.30
        for <k.kozlowski.k+kernel@gmail.com>
        (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);
        Tue, 12 Apr 2022 03:31:30 -0700 (PDT)
Received-SPF: pass (google.com: domain of srs0=siib=uw=mediatek.com=jason-jh.lin@kernel.org designates 2604:1380:4601:e00::1 as permitted sender) client-ip=2604:1380:4601:e00::1;
Authentication-Results: mx.google.com;
       spf=pass (google.com: domain of srs0=siib=uw=mediatek.com=jason-jh.lin@kernel.org designates 2604:1380:4601:e00::1 as permitted sender) smtp.mailfrom="SRS0=SiiB=UW=mediatek.com=jason-jh.lin@kernel.org";
       dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=QUARANTINE) header.from=mediatek.com
Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id C63D9B81CA1 for <k.kozlowski.k+kernel@gmail.com>; Tue, 12 Apr 2022 10:31:29 +0000 (UTC)
Received: by smtp.kernel.org (Postfix) id 8CA9AC385A6; Tue, 12 Apr 2022 10:31:29 +0000 (UTC)

Re: [PATCH v18 02/10] dt-bindings: arm: mediatek: mmsys: add mt8195 SoC binding

[Jason-JH Lin]

Hi Krzysztof,

Really appreciate your helpful information.
I hope we can figure out with IT soon.

Thank you very much!

Regards,
Jason-JH.Lin

On Mon, 2022-04-18 at 19:03 +0200, Krzysztof Kozlowski wrote:
> On 14/04/2022 05:11, Jason-JH Lin wrote:
> > Hello Rob, Krzysztof,
> > 
> > I found the dt-binding patches in this series never appeared in
> > devicetree-bindings patchwork and trigger the dt-binding check bot.
> > 
> > Do you know the reason for this?
> > Could you help me with this and let me know what should I do to
> > solve
> > this problem?
> 
> Hi,
> 
> All your emails end up regularly in my Gmail spam folder, similarly
> to
> emails from some other Mediatek people (e.g. Rex-BC Chen), so maybe
> that's the cause?
> 
> Why they end up in spam? I don't know, but it would be nice if you
> could
> work on this with your IT department. I know that corporate
> environments
> are tricky to change, but there is not much else to do. Google flags
> your emails always as spam.
> 
> You can see in the headers two DMARC failures:
> dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=QUARANTINE)
> header.from=mediatek.com
> 
> Spamming 27 recipients is maybe another reason...
> 
> Best regards,
> Krzysztof
-- 
Jason-JH Lin <jason-jh.lin@mediatek.com>