Linux I2C development
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: SP_ISW1_AT@novatek.com.tw, andi.shyti@kernel.org,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, ben_huang@novatek.com.tw,
	toby_chui@novatek.com.tw, shihpei_hsu@novatek.com.tw
Subject: Re: [PATCH 1/3] MAINTAINERS: Add entry for Novatek NT726xx SoC i2c driver.
Date: Thu, 4 Jun 2026 09:58:12 +0100	[thread overview]
Message-ID: <20260604-grievance-esophagus-a607a9d734eb@spud> (raw)
In-Reply-To: <f6cce361-47ef-4488-ac1e-5f60d3cd578b@kernel.org>

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

On Thu, Jun 04, 2026 at 09:26:56AM +0200, Krzysztof Kozlowski wrote:
> On 04/06/2026 08:04, SP_ISW1_AT@novatek.com.tw wrote:
> > CONFIDENTIALITY NOTICE: This message, including attachments, contains 
> > information which may be confidential and privileged, and is intended only for 
> > use by the addressees designated above. Unless you are the intended recipient, 
> > any use, copying, disclosure, or distribution is prohibited. If you have 
> > received the message in error, please immediately delete the message and destroy 
> 
> So can I review it or not?

Given the state of the binding patch, you probably don't want to review
it anyway!

> 
> Patch is obviously incorrect, but not sure if I am not breaking your
> confidentiality rules.
> 
> > all copies thereof and notify the sender by reply email.本郵件及任何附件均屬機 
> > 密,僅供其上指定地址之收件人使用。除非您是指定之收件人,否則請勿使用、複製、揭露 
> > 或散布本郵件之任何部份。若您錯誤地收到此郵件,請立即回覆電子郵件通知寄件人,並請 
> > 完全刪除且銷毀本郵件及其複本。

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-06-04  8:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-04  6:04 [PATCH 1/3] MAINTAINERS: Add entry for Novatek NT726xx SoC i2c driver SP_ISW1_AT
2026-06-04  6:04 ` [PATCH 2/3] dt-bindings: i2c: add Novatek NT726xx SoC i2c controller SP_ISW1_AT
2026-06-04  6:04   ` [PATCH 3/3] i2c: Add i2c-nt726xx.c i2c driver for Novatek NT726xx SoCs SP_ISW1_AT
2026-06-04  6:38     ` Wolfram Sang
2026-06-04 14:37   ` [PATCH 2/3] dt-bindings: i2c: add Novatek NT726xx SoC i2c controller Rob Herring (Arm)
2026-06-04  7:26 ` [PATCH 1/3] MAINTAINERS: Add entry for Novatek NT726xx SoC i2c driver Krzysztof Kozlowski
2026-06-04  8:58   ` Conor Dooley [this message]
     [not found]     ` <PUZPR04MB61094E3F7A824A3C8D81D8AEB7102@PUZPR04MB6109.apcprd04.prod.outlook.com>
2026-06-04 11:17       ` Krzysztof Kozlowski
2026-06-04 20:19         ` Wolfram Sang
2026-06-05  9:12           ` Krzysztof Kozlowski
2026-06-05 10:23             ` SP_ISW1_AT
2026-06-05 10:29               ` Krzysztof Kozlowski
2026-06-05 10:39                 ` SP_ISW1_AT
  -- strict thread matches above, loose matches on Subject: below --
2026-06-05  3:55 SP_ISW1_AT
2026-06-05 10:38 ` Krzysztof Kozlowski

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=20260604-grievance-esophagus-a607a9d734eb@spud \
    --to=conor@kernel.org \
    --cc=SP_ISW1_AT@novatek.com.tw \
    --cc=andi.shyti@kernel.org \
    --cc=ben_huang@novatek.com.tw \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=shihpei_hsu@novatek.com.tw \
    --cc=toby_chui@novatek.com.tw \
    /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