From: Pavel Machek <pavel@ucw.cz>
To: Alexander Dahl <ada@thorsis.com>
Cc: Hermes Zhang <chenhui.zhang@axis.com>,
Dan Murphy <dmurphy@ti.com>, Rob Herring <robh+dt@kernel.org>,
Hermes Zhang <chenhuiz@axis.com>,
kernel@axis.com, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] dt-binding: leds: Document leds-multi-gpio bindings
Date: Wed, 24 Mar 2021 09:25:52 +0100 [thread overview]
Message-ID: <20210324082551.GA15591@amd> (raw)
In-Reply-To: <558944059.12080.1616565502073@seven.thorsis.com>
[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]
On Wed 2021-03-24 06:58:21, Alexander Dahl wrote:
> Hello Hermes,
>
> > Hermes Zhang <chenhui.zhang@axis.com> hat am 24.03.2021 03:48 geschrieben:
> >
> >
> > From: Hermes Zhang <chenhuiz@axis.com>
> >
> > Document the device tree bindings of the multiple GPIOs LED driver
> > Documentation/devicetree/bindings/leds/leds-multi-gpio.yaml.
> >
> > Signed-off-by: Hermes Zhang <chenhuiz@axis.com>
> > ---
> >
> > Notes:
> > Add maxItems
>
> What about the other part of the series? I think you should send both patches together with an introduction message on both. If you only change one patch for a new version spin of the series, just send the other one unchanged.
>
Please wrap emails after 72 columns or so.
> (It makes no sense to merge the binding as long as the driver is not merged, otherwise you would end up with a binding without driver. So keeping them together should help reviewers and maintainers.)
>
This is actually okay to do if you expect discussion and not a patch
merge. Series works, too.
Best regads,
Pavel
--
http://www.livejournal.com/~pavelmachek
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2021-03-24 8:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 2:48 [PATCH v3] dt-binding: leds: Document leds-multi-gpio bindings Hermes Zhang
2021-03-24 5:58 ` Alexander Dahl
2021-03-24 6:04 ` Hermes Zhang
2021-03-24 6:15 ` Alexander Dahl
2021-03-24 8:25 ` Pavel Machek [this message]
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=20210324082551.GA15591@amd \
--to=pavel@ucw.cz \
--cc=ada@thorsis.com \
--cc=chenhui.zhang@axis.com \
--cc=chenhuiz@axis.com \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.