From: Hermes Zhang <Hermes.Zhang@axis.com>
To: Alexander Dahl <ada@thorsis.com>, Pavel Machek <pavel@ucw.cz>,
Dan Murphy <dmurphy@ti.com>, Rob Herring <robh+dt@kernel.org>
Cc: kernel <kernel@axis.com>,
"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@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 06:04:01 +0000 [thread overview]
Message-ID: <cce4da5a92d9414e87b6ac6d1d167fac@XBOX01.axis.com> (raw)
In-Reply-To: <558944059.12080.1616565502073@seven.thorsis.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.
>
> (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.)
>
Hi Alexander,
The other part is here: https://lore.kernel.org/patchwork/patch/1399875/, so do you mean I need to combine these two as one commit? Or is there anyway to link them together? Thanks.
I'm first time to commit a new driver, sorry for that.
Best Regards,
Hermes
next prev parent reply other threads:[~2021-03-24 6:04 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 [this message]
2021-03-24 6:15 ` Alexander Dahl
2021-03-24 8:25 ` Pavel Machek
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=cce4da5a92d9414e87b6ac6d1d167fac@XBOX01.axis.com \
--to=hermes.zhang@axis.com \
--cc=ada@thorsis.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=pavel@ucw.cz \
--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;
as well as URLs for NNTP newsgroup(s).