linux-next: trees being removed

linux-next: trees being removed

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 2231 bytes --]

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
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
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

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: trees being removed

[Jason A. Donenfeld]

Branch updated on random. Please do not remove.

Re: linux-next: trees being removed

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 202 bytes --]

Hi Jason,

On Wed, 24 Jan 2024 03:10:09 +0100 "Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
>
> Branch updated on random. Please do not remove.

OK, no worries.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: trees being removed

[Mike Marshall]

We are active with Orangefs, both on the userspace
side and in the kernel... I might only run xfstests to
make sure we're not regressing as kernel code
changes through numerous development cycles,
but we do intend to continue contributing in the
future...

-Mike

On Tue, Jan 23, 2024 at 9:01 PM Stephen Rothwell <sfr@canb.auug.org.au> 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
> 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
> 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

Re: linux-next: trees being removed

[Lee Jones]

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 [李琼斯]

Re: linux-next: trees being removed

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 516 bytes --]

Hi Mike,

On Wed, 24 Jan 2024 10:41:50 -0500 Mike Marshall <hubcap@omnibond.com> wrote:
>
> We are active with Orangefs, both on the userspace
> side and in the kernel... I might only run xfstests to
> make sure we're not regressing as kernel code
> changes through numerous development cycles,
> but we do intend to continue contributing in the
> future...

OK, restored.

If you just do a fast forward merge of v6.8-rc1^0, the I won't bother you
for another year :-)
-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: trees being removed

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 569 bytes --]

Hi Lee,

On Wed, 24 Jan 2024 15:50:46 +0000 Lee Jones <lee@kernel.org> wrote:
>
> > 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.
> 
> > 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.

Both restored.

> I'll update them both now if it helps.

That will keep them off my radar for a year :-)

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: trees being removed

[Jean Delvare]

Hi Stephen,

On Wed, 2024-01-24 at 13:01 +1100, 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)
> -----------------------------------------
> (...)
> dmi                     2022-09-23 14:53:14 +0200
>   git://git.kernel.org/pub/scm/linux/kernel/git/jdelvare/staging.git#dmi-for-next

This is still where I would put updates to the DMI subsystem, but it
turns out there haven't been any for some time now, and I'm not aware
of any pending issue.

Out of curiosity, why do inactive branches bother you?

I can certainly update that branch if it makes your life easier.

-- 
Jean Delvare
SUSE L3 Support

Re: linux-next: trees being removed

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]

Hi Jean,

On Tue, 06 Feb 2024 11:50:44 +0100 Jean Delvare <jdelvare@suse.de> wrote:
>
> On Wed, 2024-01-24 at 13:01 +1100, Stephen Rothwell wrote:
> > 
> > Tree                    Last commit date
> >   URL
> >   commits (if any)
> > -----------------------------------------
> > (...)
> > dmi                     2022-09-23 14:53:14 +0200
> >   git://git.kernel.org/pub/scm/linux/kernel/git/jdelvare/staging.git#dmi-for-next  
> 
> This is still where I would put updates to the DMI subsystem, but it
> turns out there haven't been any for some time now, and I'm not aware
> of any pending issue.

I am happy to restore it if you want.

> Out of curiosity, why do inactive branches bother you?

It is mostly just a way to get rid of abandoned trees.  Also, one of
the checks I do requires me to reference all the commits between the
merge base of each tree and Linus' tree.  If the base (and top commit)
of a tree has not been updated for a year, that means checking 40,000+
commits which takes a noticeable amount of time.  Also just merging
such a tree has a noticeable delay.  An empty tree (relative to Linus'
tree) doesn't cost much, of course.

> I can certainly update that branch if it makes your life easier.

Yeah, even just resetting it to Linus' tree at each -rc1 will help.
 

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: trees being removed

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1488 bytes --]

Hi all,

On Wed, 27 Mar 2024 10:13:09 +1100 Stephen Rothwell <sfr@canb.auug.org.au> 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
>   comits (if any)
> ----			----------------
> ecryptfs		2023-03-24 17:26:44 -0500
>   git://git.kernel.org/pub/scm/linux/kernel/git/tyhicks/ecryptfs.git#next
>   c1cc2db21607 ("ecryptfs: keystore: Fix typo 'the the' in comment")
>   a3d78fe3e1ae ("fs: ecryptfs: comment typo fix")
> fscrypt-current		2023-03-18 21:08:03 -0700
>   git://git.kernel.org/pub/scm/fs/fscrypt/linux.git#for-current
> fsverity-current	2023-03-15 22:50:41 -0700
>   git://git.kernel.org/pub/scm/fs/fsverity/linux.git#for-current
> modules-fixes		2023-02-06 08:45:55 -0800
>   git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git#modules-linus
> rtc-fixes		2023-01-23 23:33:47 +0100
>   git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git#rtc-fixes
> tee-fixes		2023-02-12 14:10:17 -0800
>   https://git.linaro.org/people/jens.wiklander/linux-tee.git#fixes
> ubifs-fixes		2023-01-21 16:27:01 -0800
>   git://git.kernel.org/pub/scm/linux/kernel/git/rw/ubifs.git#fixes

OK, I have removed just the ecryptfs, modules-fixes, tee-fixes and
ubifs-fixes trees.  Please just ask if you want them reinstated.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: trees being removed

[Richard Weinberger]

----- Ursprüngliche Mail -----
> Von: "Alexandre Belloni" <alexandre.belloni@bootlin.com>
>> > ubifs-fixes		2023-01-21 16:27:01 -0800
>> >   git://git.kernel.org/pub/scm/linux/kernel/git/rw/ubifs.git#fixes
>> 
>> fscrypt-current and fsverity-current are technically still in use.  I just
>> haven't used them recently because there haven't been any bug fixes that needed
>> to go in while other commits were already applied for the next merge window.
>> 
>> I've updated them to v6.9-rc1.
>> 
>> I'd guess that some of those *-fixes branches have something similar going on,
>> where they may be rarely used fixes branches as opposed to the main development
>> branch.
>> 
> 
> This is exactly my case. I don't mind my branch being dropped and I can
> ask to add it back once I have urgent fixes.

Same here. It turned out that the next branch is good enough for me.

Thanks,
//richard

Re: linux-next: trees being removed

[Alexandre Belloni]

On 27/03/2024 22:18:19+1100, Stephen Rothwell wrote:
> Hi Alexandre,
> 
> On Wed, 27 Mar 2024 11:04:21 +0100 Alexandre Belloni <alexandre.belloni@bootlin.com> wrote:
> >
> > This is exactly my case. I don't mind my branch being dropped and I can
> > ask to add it back once I have urgent fixes.
> 
> Or you could just update it to -rc1 every merge window or so and it
> will hang around.  I don't mind keeping branches around that will get
> used sometime.  I just don't like them being too old.

I've done that now and I'll try to remember to update at each -rc1.



-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

Re: linux-next: trees being removed

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 467 bytes --]

Hi Alexandre,

On Wed, 27 Mar 2024 11:04:21 +0100 Alexandre Belloni <alexandre.belloni@bootlin.com> wrote:
>
> This is exactly my case. I don't mind my branch being dropped and I can
> ask to add it back once I have urgent fixes.

Or you could just update it to -rc1 every merge window or so and it
will hang around.  I don't mind keeping branches around that will get
used sometime.  I just don't like them being too old.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: trees being removed

[Alexandre Belloni]

On 26/03/2024 21:16:53-0700, Eric Biggers wrote:
> On Wed, Mar 27, 2024 at 10:13:09AM +1100, 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
> >   comits (if any)
> > ----			----------------
> > ecryptfs		2023-03-24 17:26:44 -0500
> >   git://git.kernel.org/pub/scm/linux/kernel/git/tyhicks/ecryptfs.git#next
> >   c1cc2db21607 ("ecryptfs: keystore: Fix typo 'the the' in comment")
> >   a3d78fe3e1ae ("fs: ecryptfs: comment typo fix")
> > fscrypt-current		2023-03-18 21:08:03 -0700
> >   git://git.kernel.org/pub/scm/fs/fscrypt/linux.git#for-current
> > fsverity-current	2023-03-15 22:50:41 -0700
> >   git://git.kernel.org/pub/scm/fs/fsverity/linux.git#for-current
> > modules-fixes		2023-02-06 08:45:55 -0800
> >   git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git#modules-linus
> > rtc-fixes		2023-01-23 23:33:47 +0100
> >   git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git#rtc-fixes
> > tee-fixes		2023-02-12 14:10:17 -0800
> >   https://git.linaro.org/people/jens.wiklander/linux-tee.git#fixes
> > ubifs-fixes		2023-01-21 16:27:01 -0800
> >   git://git.kernel.org/pub/scm/linux/kernel/git/rw/ubifs.git#fixes
> 
> fscrypt-current and fsverity-current are technically still in use.  I just
> haven't used them recently because there haven't been any bug fixes that needed
> to go in while other commits were already applied for the next merge window.
> 
> I've updated them to v6.9-rc1.
> 
> I'd guess that some of those *-fixes branches have something similar going on,
> where they may be rarely used fixes branches as opposed to the main development
> branch.
> 

This is exactly my case. I don't mind my branch being dropped and I can
ask to add it back once I have urgent fixes.

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

Re: linux-next: trees being removed

[Eric Biggers]

On Wed, Mar 27, 2024 at 10:13:09AM +1100, 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
>   comits (if any)
> ----			----------------
> ecryptfs		2023-03-24 17:26:44 -0500
>   git://git.kernel.org/pub/scm/linux/kernel/git/tyhicks/ecryptfs.git#next
>   c1cc2db21607 ("ecryptfs: keystore: Fix typo 'the the' in comment")
>   a3d78fe3e1ae ("fs: ecryptfs: comment typo fix")
> fscrypt-current		2023-03-18 21:08:03 -0700
>   git://git.kernel.org/pub/scm/fs/fscrypt/linux.git#for-current
> fsverity-current	2023-03-15 22:50:41 -0700
>   git://git.kernel.org/pub/scm/fs/fsverity/linux.git#for-current
> modules-fixes		2023-02-06 08:45:55 -0800
>   git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git#modules-linus
> rtc-fixes		2023-01-23 23:33:47 +0100
>   git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git#rtc-fixes
> tee-fixes		2023-02-12 14:10:17 -0800
>   https://git.linaro.org/people/jens.wiklander/linux-tee.git#fixes
> ubifs-fixes		2023-01-21 16:27:01 -0800
>   git://git.kernel.org/pub/scm/linux/kernel/git/rw/ubifs.git#fixes

fscrypt-current and fsverity-current are technically still in use.  I just
haven't used them recently because there haven't been any bug fixes that needed
to go in while other commits were already applied for the next merge window.

I've updated them to v6.9-rc1.

I'd guess that some of those *-fixes branches have something similar going on,
where they may be rarely used fixes branches as opposed to the main development
branch.

- Eric

linux-next: trees being removed

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]

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
  comits (if any)
----			----------------
ecryptfs		2023-03-24 17:26:44 -0500
  git://git.kernel.org/pub/scm/linux/kernel/git/tyhicks/ecryptfs.git#next
  c1cc2db21607 ("ecryptfs: keystore: Fix typo 'the the' in comment")
  a3d78fe3e1ae ("fs: ecryptfs: comment typo fix")
fscrypt-current		2023-03-18 21:08:03 -0700
  git://git.kernel.org/pub/scm/fs/fscrypt/linux.git#for-current
fsverity-current	2023-03-15 22:50:41 -0700
  git://git.kernel.org/pub/scm/fs/fsverity/linux.git#for-current
modules-fixes		2023-02-06 08:45:55 -0800
  git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git#modules-linus
rtc-fixes		2023-01-23 23:33:47 +0100
  git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git#rtc-fixes
tee-fixes		2023-02-12 14:10:17 -0800
  https://git.linaro.org/people/jens.wiklander/linux-tee.git#fixes
ubifs-fixes		2023-01-21 16:27:01 -0800
  git://git.kernel.org/pub/scm/linux/kernel/git/rw/ubifs.git#fixes

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]