From: Mark Brown <broonie@kernel.org>
To: Mike Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Brian Masney <bmasney@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: Missing signoff in the clk tree
Date: Mon, 26 Oct 2026 14:03:24 +0000 [thread overview]
Message-ID: <at9drMPrv1IvPovj@sirena.co.uk> (raw)
In-Reply-To: <atZqw7pdZjMwahdf@sirena.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]
On Mon, Oct 19, 2026 at 08:08:51PM +0100, Mark Brown wrote:
> On Mon, Oct 12, 2026 at 08:01:34PM +0100, Mark Brown wrote:
> > On Mon, Oct 05, 2026 at 02:53:25PM +0200, Mark Brown wrote:
> > > On Fri, Oct 02, 2026 at 07:12:40PM +0100, Mark Brown wrote:
> > > > Commits
> > > >
> > > > d31b7d87d1b28 ("clk: nuvoton: ma35d1: Add missing WDT/WWDT parent clocks")
> > > > 488d2cfdf3c99 ("dt-bindings: clock: ma35d1: Add missing WDT/WWDT parent clocks")
> > > > 9546425453234 ("dt-bindings: clock: ma35d1: Drop CLK_MAX_IDX define")
> > > > ea2ee01da5555 ("dt-bindings: clock: ma35d1: Document the missing crystal inputs")
> > > > 35ba0118dac01 ("clk: nuvoton: ma35d1: Keep the clock count in the driver")
> > > > e92291a009f7c ("clk: clk-gpio: do not blame the DT property on probe deferral")
> > > >
> > > > are missing a Signed-off-by from their committers
> > >
> > > This issue is still present today.
> >
> > And today.
>
> And today.
And today. I see the commits were actually done by Brian (CCed), who
also appears to be a new maintainer for the clock tree - I guess the
contacts for the tree need updating to include him?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-10-26 14:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 18:12 Missing signoff in the clk tree Mark Brown
2026-10-05 12:53 ` Mark Brown
2026-10-12 19:01 ` Mark Brown
2026-10-19 19:08 ` Mark Brown
2026-10-26 14:03 ` Mark Brown [this message]
2026-10-26 15:08 ` Brian Masney
2026-10-26 18:15 ` Mark Brown
2026-10-26 23:57 ` Brian Masney
2026-10-28 11:50 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2026-04-13 10:41 Mark Brown
2026-04-13 16:51 ` Mark Brown
2026-04-20 13:31 ` Mark Brown
2026-02-03 11:30 Mark Brown
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=at9drMPrv1IvPovj@sirena.co.uk \
--to=broonie@kernel.org \
--cc=bmasney@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@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.