From: Andrew Lunn <andrew@lunn.ch>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
Ariel D'Alessandro <ariel.dalessandro@collabora.com>,
andrew+netdev@lunn.ch, conor+dt@kernel.org, kernel@collabora.com,
krzk+dt@kernel.org, angelogioacchino.delregno@collabora.com,
kuba@kernel.org, devicetree@vger.kernel.org,
linux-bluetooth@vger.kernel.org, davem@davemloft.net,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, edumazet@google.com
Subject: Re: [PATCH v3] dt-bindings: net: Convert Marvell 8897/8997 bindings to DT schema
Date: Tue, 7 Oct 2025 14:18:51 +0200 [thread overview]
Message-ID: <89bb83ec-200c-4ed6-bfd8-ac55375e4ee1@lunn.ch> (raw)
In-Reply-To: <CABBYNZKxGNXS2m7_VAf1d_Ci3uW4xG2NamXZ0UVaHvKvHi07Jg@mail.gmail.com>
> > > > Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
> > > >
> > > > You'll probably have to resend this after rc1.
> > >
> > > In that case I'd like to have a Fixes tag so I can remember to send it
> > > as rc1 is tagged.
> >
> > A Fixes tag is not appropriate for a conversion to DT schema.
>
> Ok, but then how do you justify merging it for an RC? Or I'm
> misunderstanding and that should just be merged to bluetooth-next and
> wait for the next merge window? In that case I can just merge it right
> away.
Most subsystems don't accept new patches during the merge window
because they will need to do a rebase when -rc1 is pushed. And
rebasing of patches is frowned upon.
By requesting the developers to repost after -rc1 is out, and the
subsystem tree has been updated to -rc1, the Maintainers avoids the
rebase, and pushes the work to the developer to rebase and retest,
leaving the Maintainers to do more useful work.
Andrew
next prev parent reply other threads:[~2025-10-07 12:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 18:33 [PATCH v3] dt-bindings: net: Convert Marvell 8897/8997 bindings to DT schema Ariel D'Alessandro
2025-10-02 19:14 ` Rob Herring (Arm)
2025-10-02 19:17 ` Luiz Augusto von Dentz
2025-10-03 13:37 ` Rob Herring
2025-10-03 14:32 ` Luiz Augusto von Dentz
2025-10-07 12:18 ` Andrew Lunn [this message]
2025-10-08 19:22 ` Rob Herring
2025-10-24 17:10 ` Rob Herring
2025-10-24 17:30 ` patchwork-bot+bluetooth
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=89bb83ec-200c-4ed6-bfd8-ac55375e4ee1@lunn.ch \
--to=andrew@lunn.ch \
--cc=andrew+netdev@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=ariel.dalessandro@collabora.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).