mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Delphine CC Chiu <Delphine_CC_Chiu@wiwynn.com>,
	patrick@stwcx.xyz, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
	Andrew Jeffery <andrew@codeconstruct.com.au>
Cc: Ricky CX Wu <ricky.cx.wu.wiwynn@gmail.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v16 1/3] ARM: dts: aspeed: yosemite4: Revise i2c-mux devices
Date: Fri, 6 Sep 2024 12:04:15 +0200	[thread overview]
Message-ID: <e89bf774-12e3-4360-919e-f93148ce3456@kernel.org> (raw)
In-Reply-To: <20240906092438.1047225-2-Delphine_CC_Chiu@wiwynn.com>

On 06/09/2024 11:24, Delphine CC Chiu wrote:
> From: Ricky CX Wu <ricky.cx.wu.wiwynn@gmail.com>
> 
> Revise Yosemite 4 devicetree for devices behind i2c-mux
> - Add gpio and eeprom behind i2c-mux
> - Remove redundant idle-state setting for i2c-mux
> - Revise address of max31790 devices after i2c-mux.
> 
> Signed-off-by: Ricky CX Wu <ricky.cx.wu.wiwynn@gmail.com>

Missing SoB. On all your patchsets.

Best regards,
Krzysztof


  reply	other threads:[~2024-09-06 10:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-06  9:24 [PATCH v16 0/3] Add i2c-mux and eeprom devices for Meta Yosemite4 Delphine CC Chiu
2024-09-06  9:24 ` [PATCH v16 1/3] ARM: dts: aspeed: yosemite4: Revise i2c-mux devices Delphine CC Chiu
2024-09-06 10:04   ` Krzysztof Kozlowski [this message]
2024-09-09  1:34     ` Delphine_CC_Chiu/WYHQ/Wiwynn
2024-09-06  9:24 ` [PATCH v16 2/3] ARM: dts: aspeed: yosemite4: add mctp config and sensors for NIC Delphine CC Chiu
2024-09-06  9:24 ` [PATCH v16 3/3] ARM: dts: aspeed: yosemite4: add fan led config Delphine CC Chiu
2024-09-06 19:37 ` [PATCH v16 0/3] Add i2c-mux and eeprom devices for Meta Yosemite4 Rob Herring (Arm)

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=e89bf774-12e3-4360-919e-f93148ce3456@kernel.org \
    --to=krzk@kernel.org \
    --cc=Delphine_CC_Chiu@wiwynn.com \
    --cc=andrew@codeconstruct.com.au \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=joel@jms.id.au \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patrick@stwcx.xyz \
    --cc=ricky.cx.wu.wiwynn@gmail.com \
    --cc=robh@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

all inboxes | Powered by JetHome®