From: Dennis Zhou <dennis@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Linux Next Mailing List" <linux-next@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Andreas Larsson" <andreas@gaisler.com>,
"Christoph Lameter" <cl@linux-foundation.org>,
"Chuck Lever" <chuck.lever@oracle.com>,
"Dipen Patel" <dipenp@nvidia.com>,
"Gabriel Krisman Bertazi" <krisman@collabora.com>,
"Ingo Molnar" <mingo@kernel.org>,
"Jean Delvare" <jdelvare@suse.de>, "Lee Jones" <lee@kernel.org>,
"Masami Hiramatsu" <mhiramat@kernel.org>,
"Matthew Wilcox" <willy@infradead.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Oded Gabbay" <ogabbay@kernel.org>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Tejun Heo" <tj@kernel.org>, "Tyler Hicks" <code@tyhicks.com>,
"Uwe Kleine-König" <ukleinek@kernel.org>
Subject: Re: linux-next: trees being removed
Date: Fri, 19 Dec 2025 16:36:14 -0800 [thread overview]
Message-ID: <aUXvfrACjil_Muv0@snowbird> (raw)
In-Reply-To: <20251215184126.39dae2c7@canb.auug.org.au>
Hi Stephen,
On Mon, Dec 15, 2025 at 06:41:26PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> The following trees are going to be removed from linux-next because they
> have not been updated in more than a year. If you want a tree kept,
> please just reply and let me know (and update its branch). If you want
> a tree restored after it has been removed, just let me know (and update
> its branch).
>
> Tree Last commit date
> URL
> comits (if any)
> ---- ----------------
> accel 2024-05-03 11:00:53 +1000
> https://git.kernel.org/pub/scm/linux/kernel/git/ogabbay/linux.git#habanalabs-next
> clang-format 2024-08-02 13:20:31 +0200
> https://github.com/ojeda/linux.git#clang-format
> compiler-attributes 2024-09-15 16:57:56 +0200
> https://github.com/ojeda/linux.git#compiler-attributes
> dmi 2024-05-14 11:23:02 +0200
> https://git.kernel.org/pub/scm/linux/kernel/git/jdelvare/staging.git#dmi-for-next
> ecryptfs 2024-10-21 01:47:22 -0500
> https://git.kernel.org/pub/scm/linux/kernel/git/tyhicks/ecryptfs.git#next
> b06c72107980 ("ecryptfs: keystore: Fix typo 'the the' in comment")
> da22e0dc323c ("fs: ecryptfs: comment typo fix")
> 68c119aecdcd ("ecryptfs: Fix packet format comment in parse_tag_67_packet()")
> fba133a34118 ("ecryptfs: Remove unused declartion ecryptfs_fill_zeros()")
> exportfs 2024-11-17 14:15:08 -0800
> https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git#exportfs-next
> hte 2024-06-19 12:24:03 -0700
> https://git.kernel.org/pub/scm/linux/kernel/git/pateldipen1984/linux.git#for-next
> percpu 2024-10-07 11:33:26 -0700
> https://git.kernel.org/pub/scm/linux/kernel/git/dennis/percpu.git#for-next
> siox 2024-03-08 22:01:10 +0100
I've not been very active for the last few years and luckily it
coincided with less work in the percpu area. I've been sending small
patches through Andrew but I think I'd prefer to keep the tree as I hope
to do more active work in 2026.
I've just updated the for-next branch albiet just with 6.19-rc1.
Thanks,
Dennis
next prev parent reply other threads:[~2025-12-20 0:36 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 7:41 linux-next: trees being removed Stephen Rothwell
2025-12-15 14:55 ` Chuck Lever
2025-12-15 21:21 ` Stephen Rothwell
2025-12-15 15:43 ` Lee Jones
2025-12-15 18:09 ` Uwe Kleine-König
2025-12-16 5:19 ` Stephen Rothwell
2025-12-16 14:04 ` Thorsten Scherer
2025-12-18 23:40 ` Gabriel Krisman Bertazi
2025-12-18 23:57 ` Stephen Rothwell
2025-12-19 10:36 ` Miguel Ojeda
2025-12-19 10:41 ` Andreas Larsson
2025-12-19 11:53 ` Krzysztof Kozlowski
2025-12-19 12:01 ` Krzysztof Kozlowski
2025-12-20 0:36 ` Dennis Zhou [this message]
2026-01-05 21:51 ` Dipen Patel
2026-01-05 22:08 ` Stephen Rothwell
2026-02-09 12:33 ` Jean Delvare
2026-02-10 5:19 ` Stephen Rothwell
2026-02-10 12:25 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2025-02-11 22:56 Stephen Rothwell
2025-02-12 16:32 ` Vineet Gupta
2025-02-16 11:11 ` Stephen Rothwell
2025-02-19 19:58 ` Vineet Gupta
2025-02-19 21:52 ` Stephen Rothwell
2025-02-16 11:42 ` Stephen Rothwell
2025-03-05 21:34 ` Nick Terrell
2025-03-05 21:47 ` Stephen Rothwell
2024-08-12 22:51 Stephen Rothwell
2024-08-13 5:13 ` Peter Rosin
2024-08-13 6:59 ` Stephen Rothwell
2024-08-14 10:06 ` Vignesh Raghavendra
2024-08-14 10:55 ` Stephen Rothwell
2024-08-19 22:36 ` Stephen Rothwell
2024-03-26 23:13 Stephen Rothwell
2024-03-27 4:16 ` Eric Biggers
2024-03-27 10:04 ` Alexandre Belloni
2024-03-27 11:18 ` Stephen Rothwell
2024-03-27 12:46 ` Alexandre Belloni
2024-03-27 21:33 ` Richard Weinberger
2024-04-01 21:13 ` Stephen Rothwell
2024-01-24 2:01 Stephen Rothwell
2024-01-24 2:10 ` Jason A. Donenfeld
2024-01-24 2:32 ` Stephen Rothwell
2024-01-24 15:41 ` Mike Marshall
2024-01-24 21:49 ` Stephen Rothwell
2024-01-24 15:50 ` Lee Jones
2024-01-24 21:56 ` Stephen Rothwell
2024-02-06 10:50 ` Jean Delvare
2024-02-06 22:13 ` 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=aUXvfrACjil_Muv0@snowbird \
--to=dennis@kernel.org \
--cc=andreas@gaisler.com \
--cc=chuck.lever@oracle.com \
--cc=cl@linux-foundation.org \
--cc=code@tyhicks.com \
--cc=dipenp@nvidia.com \
--cc=jdelvare@suse.de \
--cc=krisman@collabora.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=ogabbay@kernel.org \
--cc=ojeda@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
--cc=tj@kernel.org \
--cc=ukleinek@kernel.org \
--cc=willy@infradead.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