Linux-mediatek Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jason-JH Lin <jason-jh.lin@mediatek.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Chun-Kuang Hu <chunkuang.hu@kernel.org>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>
Cc: "Rex-BC Chen (陳柏辰)" <Rex-BC.Chen@mediatek.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH v18 02/10] dt-bindings: arm: mediatek: mmsys: add mt8195 SoC binding
Date: Tue, 19 Apr 2022 09:53:46 +0800	[thread overview]
Message-ID: <b518577296cb24749c6b76a6209c7e95b84e8ac0.camel@mediatek.com> (raw)
In-Reply-To: <ff8a2ede-1489-0412-2425-3191f9fd9026@kernel.org>

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>


_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

  reply	other threads:[~2022-04-19  1:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12 10:31 [PATCH v18 00/10] Add Mediatek Soc DRM (vdosys0) support for mt8195 jason-jh.lin
2022-04-12 10:31 ` [PATCH v18 01/10] dt-bindings: arm: mediatek: mmsys: add power and gce properties jason-jh.lin
2022-04-12 10:31 ` [PATCH v18 02/10] dt-bindings: arm: mediatek: mmsys: add mt8195 SoC binding jason-jh.lin
2022-04-14  3:11   ` Jason-JH Lin
2022-04-18 17:03     ` Krzysztof Kozlowski
2022-04-19  1:53       ` Jason-JH Lin [this message]
2022-04-12 10:31 ` [PATCH v18 03/10] soc: mediatek: add mtk-mmsys support for mt8195 vdosys0 jason-jh.lin
2022-04-13  6:07   ` Dan Carpenter
2022-04-13  8:43     ` Jason-JH Lin
2022-04-12 10:31 ` [PATCH v18 04/10] soc: mediatek: add mtk-mutex " jason-jh.lin
2022-04-12 10:31 ` [PATCH v18 05/10] drm/mediatek: add DSC support for mediatek-drm jason-jh.lin
2022-04-12 10:31 ` [PATCH v18 06/10] drm/mediatek: add MERGE " jason-jh.lin
2022-04-12 10:31 ` [PATCH v18 07/10] drm/mediatek: add mediatek-drm of vdosys0 support for mt8195 jason-jh.lin
2022-04-14 15:31   ` kernel test robot
2022-04-15  6:27     ` Jason-JH Lin
2022-04-12 10:31 ` [PATCH v18 08/10] soc: mediatek: add DDP_DOMPONENT_DITHER0 enum for mt8195 vdosys0 jason-jh.lin
2022-04-15  6:24   ` Rex-BC Chen
2022-04-15  8:13     ` Jason-JH Lin
2022-04-12 10:31 ` [PATCH v18 09/10] drm/mediatek: add postfix 0 to DDP_COMPONENT_DITHER " jason-jh.lin
2022-04-12 10:31 ` [PATCH v18 10/10] soc: mediatek: remove DDP_DOMPONENT_DITHER enum jason-jh.lin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b518577296cb24749c6b76a6209c7e95b84e8ac0.camel@mediatek.com \
    --to=jason-jh.lin@mediatek.com \
    --cc=Rex-BC.Chen@mediatek.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=chunkuang.hu@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=robh+dt@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox