From: Lee Jones <lee@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>,
David Miller <davem@davemloft.net>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Hector Martin <marcan@marcan.st>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
Jean Delvare <jdelvare@suse.de>,
Micah Morton <mortonm@chromium.org>,
Mike Marshall <hubcap@omnibond.com>, Pavel Machek <pavel@ucw.cz>,
Theodore Ts'o <tytso@mit.edu>
Subject: Re: linux-next: trees being removed
Date: Wed, 24 Jan 2024 15:50:46 +0000 [thread overview]
Message-ID: <20240124155046.GB74950@google.com> (raw)
In-Reply-To: <20240124130101.428c09a3@canb.auug.org.au>
On Wed, 24 Jan 2024, Stephen Rothwell wrote:
> 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 restored,
> just let me know (and update its branch).
>
> Tree Last commit date
> URL
> commits (if any)
> -----------------------------------------
> asahi-soc-fixes 2022-08-14 15:50:18 -0700
> https://github.com/AsahiLinux/linux.git#asahi-soc/fixes
> backlight-fixes 2023-01-01 13:53:16 -0800
> git://git.kernel.org/pub/scm/linux/kernel/git/lee/backlight.git#for-backlight-fixes
This is still active, when it's needed.
> broadcom-fixes 2022-10-16 15:36:24 -0700
> https://github.com/Broadcom/stblinux.git#fixes
> dmi 2022-09-23 14:53:14 +0200
> git://git.kernel.org/pub/scm/linux/kernel/git/jdelvare/staging.git#dmi-for-next
> leds 2022-12-25 13:41:39 -0800
> git://git.kernel.org/pub/scm/linux/kernel/git/pavel/linux-leds.git#for-next
> mfd-fixes 2023-01-01 13:53:16 -0800
> git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git#for-mfd-fixes
As is this one.
I'll update them both now if it helps.
> orangefs 2022-12-07 15:18:30 -0500
> git://git.kernel.org/pub/scm/linux/kernel/git/hubcap/linux#for-next
> random 2023-01-04 12:11:29 -0800
> git://git.kernel.org/pub/scm/linux/kernel/git/crng/random.git#master
> safesetid 2022-07-15 18:24:42 +0000
> https://github.com/micah-morton/linux.git#safesetid-next
> sparc 2022-09-30 11:58:23 +0100
> git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc.git#master
> 2d2b17d08bfc ("sparc: Unbreak the build")
> (This commit has been included in Linus' tree as part of another commit)
> userns 2022-11-30 12:54:24 -0600
> git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git#for-next
> 54e1011bd95a ("sysctl: Allow change system v ipc sysctls inside ipc namespace")
> f9b90c2062b2 ("docs: Add information about ipc sysctls limitations")
> 7608b6a72ed0 ("sysctl: Allow to change limits for posix messages queues")
> a799be9bafe3 ("ipc/ipc_sysctl: Add missing include of linux/cred.h")
> b895e6689ebf ("sysctl: Fix mq permission check")
> 295227b10192 ("ucount: Fix atomic_long_inc_below argument type")
> b4b11b58cd02 ("ucount: Use atomic_long_try_cmpxchg in atomic_long_inc_below")
> (only these last 2 commits actually change anything in Linus' tree)
>
> --
> Cheers,
> Stephen Rothwell
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2024-01-24 15:50 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 2:01 linux-next: trees being removed 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 [this message]
2024-01-24 21:56 ` Stephen Rothwell
2024-02-06 10:50 ` Jean Delvare
2024-02-06 22:13 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
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-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
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
2025-12-15 7:41 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
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
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=20240124155046.GB74950@google.com \
--to=lee@kernel.org \
--cc=Jason@zx2c4.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=f.fainelli@gmail.com \
--cc=hubcap@omnibond.com \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=mortonm@chromium.org \
--cc=pavel@ucw.cz \
--cc=sfr@canb.auug.org.au \
--cc=tytso@mit.edu \
/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