From: Mark Brown <broonie@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Nov 9
Date: Mon, 9 Nov 2026 22:35:12 +0000 [thread overview]
Message-ID: <970f8568-bc47-469b-8ff3-34bb2eb7a2d9@sirena.org.uk> (raw)
In-Reply-To: <20261109200324.GA950470-robh@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 384 bytes --]
On Mon, Nov 09, 2026 at 02:03:24PM -0600, Rob Herring wrote:
> It looks like a number of trees are missing today. For example, clk,
> reset, and i2c trees have fixes, but not next branches.
Hrm, unfortunate. Sometimes things do fail to update (which was more
likely than usual today due to hotel WiFi) but we should still have the
last update. I'll have a look tomorrow.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-11-09 22:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 15:03 Mark Brown
2026-11-09 20:03 ` Rob Herring
2026-11-09 22:35 ` Mark Brown [this message]
2026-11-09 22:46 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2023-11-09 2:08 Stephen Rothwell
2022-11-09 5:37 Stephen Rothwell
2021-11-09 2:54 Stephen Rothwell
2021-11-09 2:55 ` Stephen Rothwell
2021-11-09 9:58 ` Geert Uytterhoeven
2021-11-09 11:00 ` Jan Kara
2020-11-09 7:17 Stephen Rothwell
2018-11-09 3:04 Stephen Rothwell
2017-11-09 6:42 Stephen Rothwell
2016-11-09 4:40 Stephen Rothwell
2015-11-09 3:06 Stephen Rothwell
2012-11-09 4:31 Stephen Rothwell
2011-11-09 2:58 Stephen Rothwell
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=970f8568-bc47-469b-8ff3-34bb2eb7a2d9@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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
all inboxes | Powered by JetHome®