[PATCH v3] dt-bindings: cleanup: fix duplicated 'is is' in YAML docs

[Martin Blumenstingl]

On Wed, Jul 23, 2025 at 6:30 PM Sanjay Suthar
<sanjaysuthar661996 at gmail.com> wrote:
>
> On 23/07/25 01:08, Martin Blumenstingl wrote:
>
> > On Tue, Jul 22, 2025 at 7:06 PM Sanjay Suthar
> > <sanjaysuthar661996 at gmail.com> wrote:
> >> Fix minor grammatical issues by removing duplicated "is" in two devicetree
> >> binding documents:
> >>
> >> - net/amlogic,meson-dwmac.yaml
> >> - iio/dac/ti,dac7612.yaml
> >>
> >> Signed-off-by: Sanjay Suthar <sanjaysuthar661996 at gmail.com>
> > Reviewed-by: Martin Blumenstingl <martin.blumenstingl at googlemail.com>
> >
> > Thank you for spotting and fixing this!
> >
> > To my knowledge nobody else is currently working on amlogic,meson-dwmac changes.
> > Meaning: with an ACK from the netdev or iio maintainers this patch can
> > go through any tree (iio, netdev, devicetree).
> >
> >
> > Best regards,
> > Martin
>
> Thanks for reviewing the patch. So you mentioned, now the patch can go
> through any of above mentioned tree, Is there any Action item left on my
> end related to this patch? Also will I be notified about when the patch
> will be approved and merged by the respective owner?
Apart from waiting a few days there's nothing to be done on your end.
Both the netdev and iio maintainers are fairly quick to review
patches, but they have to review a large volume. So give them some
time.

A little bit of background in case it helps understand things better.
In my opinion this patch can go through three trees, since these areas
are involved (in no particular order):
- netdev
- iio
- devicetree

If one maintainer takes a patch that somehow touches another
maintainer's area what typically happens is that the maintainers give
their Acked-by and agree on the tree through which the patch will land
in mainline (= Linux Torvalds' tree).
When the patch is picked up there's typically a mail, informing you
about the tree that it has been applied to.

In case you don't hear anything after a few days (my rule of thumb is
a week, during the merge window it can take longer though - but we're
not there yet) then please send a short gentle reminder that you're
still waiting for a reply.


Best regards,
Martin