From: Mark Brown <broonie@kernel.org>
To: Brian Masney <bmasney@redhat.com>
Cc: Mike Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
Jerome Brunet <jbrunet@baylibre.com>
Subject: Re: Missing signoff in the clk tree
Date: Mon, 26 Oct 2026 18:15:04 +0000 [thread overview]
Message-ID: <at-YqCa-RGEv7IJ4@sirena.org.uk> (raw)
In-Reply-To: <CABx5tqKQs2LFNEW7ZTwFqD66Mzv7EM+fSbqWkZ8chaWfXhheOA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 729 bytes --]
On Mon, Oct 26, 2026 at 11:08:35AM -0400, Brian Masney wrote:
> On Mon, Oct 26, 2026 at 10:03 AM Mark Brown <broonie@kernel.org> wrote:
> > 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?
> I will fix that this evening. Sorry about that.
> Jerome and I were added as the new co-maintainers and we are listed in
> the MAINTAINERS file. Is there somewhere else that we should be added
> for linux-clk?
Yes, you need to tell me about it - there's a separate list of contacts
for the various trees in -next since there isn't a 1:1 correspondance
between them.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-10-26 18:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 18:12 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
2026-10-26 15:08 ` Brian Masney
2026-10-26 18:15 ` Mark Brown [this message]
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=at-YqCa-RGEv7IJ4@sirena.org.uk \
--to=broonie@kernel.org \
--cc=bmasney@redhat.com \
--cc=jbrunet@baylibre.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®