From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Patrick Rudolph <patrick.rudolph@9elements.com>,
Peter Rosin <peda@axentia.se>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v10 1/3] dt-bindings: i2c: Add Maxim MAX735x/MAX736x variants
Date: Thu, 23 Mar 2023 13:35:52 +0100 [thread overview]
Message-ID: <04876110-1dec-dafd-cf4e-a6ed7a8b40b0@linaro.org> (raw)
In-Reply-To: <20230323115356.2602042-2-patrick.rudolph@9elements.com>
On 23/03/2023 12:53, Patrick Rudolph wrote:
> Update the pca954x bindings to add support for the Maxim MAX735x/MAX736x
> chips. The functionality will be provided by the exisintg pca954x driver.
>
> While on it make the interrupts support conditionally as not all of the
> existing chips have interrupts.
>
> For chips that are powered off by default add an optional regulator
> called vdd-supply.
>
> Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
I just received this patch sent twice - as 1/3 and 1/4 - without
changelog, no cover letter, nothing more. Also other patches are
missing, but that I could understand as intentional.
This is confusing. New submission means new version. Attach changelog
after --- explaining the changes.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-03-23 12:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 11:53 [PATCH v10 0/3] Add support for Maxim MAX735x/MAX736x variants Patrick Rudolph
2023-03-23 11:53 ` [PATCH v10 1/3] dt-bindings: i2c: Add " Patrick Rudolph
2023-03-23 12:35 ` Krzysztof Kozlowski [this message]
2023-03-23 13:58 ` Rob Herring
2023-03-23 11:53 ` [PATCH v10 2/3] i2c: muxes: pca954x: Add MAX735x/MAX736x support Patrick Rudolph
2023-03-23 11:53 ` [PATCH v10 3/3] i2c: muxes: pca954x: Add regulator support Patrick Rudolph
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=04876110-1dec-dafd-cf4e-a6ed7a8b40b0@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick.rudolph@9elements.com \
--cc=peda@axentia.se \
--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