linux-next: trees being removed

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

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

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

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

[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

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

linux-next: trees being removed

[Stephen Rothwell]

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

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
  https://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux.git#siox/for-next
unicode			2024-10-11 15:02:41 -0400
  https://git.kernel.org/pub/scm/linux/kernel/git/krisman/unicode.git#for-next
xarray			2024-09-23 15:16:41 -0400
  git://git.infradead.org/users/willy/xarray.git#main
  c88414f56c37 ("XArray: Prevent node leaks in xas_alloc()")
  6684aba0780d ("XArray: Add extra debugging check to xas_lock and friends")


These trees of fixes will be kept in any case (please let me know if
they should go):

backlight-fixes		2024-05-26 15:20:12 -0700
  https://git.kernel.org/pub/scm/linux/kernel/git/lee/backlight.git#for-backlight-fixes
sparc-fixes		2024-01-21 14:11:32 -0800
  https://git.kernel.org/pub/scm/linux/kernel/git/alarsson/linux-sparc.git#for-linus
tracefs-fixes		2024-11-01 08:57:55 -0400
  https://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git#tracefs/fixes

-- 
Cheers,
Stephen Rothwell

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

Re: linux-next: trees being removed

[Chuck Lever]

On 12/15/25 2:41 AM, 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

re: the exportfs tree: yes, that's fine with me. I asked for that to be
added to linux-next before we knew that exportfs patches would be going
through the VFS trees instead.


> 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
>   https://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux.git#siox/for-next
> unicode			2024-10-11 15:02:41 -0400
>   https://git.kernel.org/pub/scm/linux/kernel/git/krisman/unicode.git#for-next
> xarray			2024-09-23 15:16:41 -0400
>   git://git.infradead.org/users/willy/xarray.git#main
>   c88414f56c37 ("XArray: Prevent node leaks in xas_alloc()")
>   6684aba0780d ("XArray: Add extra debugging check to xas_lock and friends")
> 
> 
> These trees of fixes will be kept in any case (please let me know if
> they should go):
> 
> backlight-fixes		2024-05-26 15:20:12 -0700
>   https://git.kernel.org/pub/scm/linux/kernel/git/lee/backlight.git#for-backlight-fixes
> sparc-fixes		2024-01-21 14:11:32 -0800
>   https://git.kernel.org/pub/scm/linux/kernel/git/alarsson/linux-sparc.git#for-linus
> tracefs-fixes		2024-11-01 08:57:55 -0400
>   https://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git#tracefs/fixes
> 


-- 
Chuck Lever

Re: linux-next: trees being removed

[Stephen Rothwell]

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

Hi Chuck,

On Mon, 15 Dec 2025 09:55:16 -0500 Chuck Lever <chuck.lever@oracle.com> wrote:
>
> On 12/15/25 2:41 AM, Stephen Rothwell wrote:
> > 
> > exportfs		2024-11-17 14:15:08 -0800
> >   https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git#exportfs-next  
> 
> re: the exportfs tree: yes, that's fine with me. I asked for that to be
> added to linux-next before we knew that exportfs patches would be going
> through the VFS trees instead.

Thanks, I have removed it now.

-- 
Cheers,
Stephen Rothwell

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

Re: linux-next: trees being removed

[Lee Jones]

On Mon, 15 Dec 2025, 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
>   https://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux.git#siox/for-next
> unicode			2024-10-11 15:02:41 -0400
>   https://git.kernel.org/pub/scm/linux/kernel/git/krisman/unicode.git#for-next
> xarray			2024-09-23 15:16:41 -0400
>   git://git.infradead.org/users/willy/xarray.git#main
>   c88414f56c37 ("XArray: Prevent node leaks in xas_alloc()")
>   6684aba0780d ("XArray: Add extra debugging check to xas_lock and friends")
> 
> 
> These trees of fixes will be kept in any case (please let me know if
> they should go):
> 
> backlight-fixes		2024-05-26 15:20:12 -0700
>   https://git.kernel.org/pub/scm/linux/kernel/git/lee/backlight.git#for-backlight-fixes

Yes, please keep this one.  I have updated and pushed it.

> sparc-fixes		2024-01-21 14:11:32 -0800
>   https://git.kernel.org/pub/scm/linux/kernel/git/alarsson/linux-sparc.git#for-linus
> tracefs-fixes		2024-11-01 08:57:55 -0400
>   https://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git#tracefs/fixes

Thanks Stephen.

-- 
Lee Jones [李琼斯]

Re: linux-next: trees being removed

[Uwe Kleine-König]

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

Hello Stephen,

[trimmed Cc and added Thorsten and the Pengutronix Kernel Team]

On Mon, Dec 15, 2025 at 06:41:26PM +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.
> [...]
> siox			2024-03-08 22:01:10 +0100
>   https://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux.git#siox/for-next

this is fine. The last patches to drivers/siox went in through Greg and
I'm not involved in siox development any more. (Otherwise I would have
opposed 53d2bf583c6b6326d751d0f0dceba76109dfb0f9 :-)

Best regards
Uwe

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

Re: linux-next: trees being removed

[Stephen Rothwell]

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

Hi Uwe,

On Mon, 15 Dec 2025 19:09:53 +0100 Uwe Kleine-König <ukleinek@kernel.org> wrote:
>
> [trimmed Cc and added Thorsten and the Pengutronix Kernel Team]
> 
> On Mon, Dec 15, 2025 at 06:41:26PM +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.
> > [...]
> > siox			2024-03-08 22:01:10 +0100
> >   https://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux.git#siox/for-next  
> 
> this is fine. The last patches to drivers/siox went in through Greg and
> I'm not involved in siox development any more. (Otherwise I would have
> opposed 53d2bf583c6b6326d751d0f0dceba76109dfb0f9 :-)

Thanks. Removed from tomorrow.

-- 
Cheers,
Stephen Rothwell

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

Re: linux-next: trees being removed

[Thorsten Scherer]

Hello Uwe, Hello Stephen,

On Mon, Dec 15, 2025 at 07:09:53PM +0100, Uwe Kleine-König wrote:
> Hello Stephen,
> 
> [trimmed Cc and added Thorsten and the Pengutronix Kernel Team]
> 
> On Mon, Dec 15, 2025 at 06:41:26PM +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.
> > [...]
> > siox			2024-03-08 22:01:10 +0100
> >   https://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux.git#siox/for-next
> 
> this is fine. The last patches to drivers/siox went in through Greg and
> I'm not involved in siox development any more. (Otherwise I would have
> opposed 53d2bf583c6b6326d751d0f0dceba76109dfb0f9 :-)

@uwe: thanks for cc'ing me and puttin this on my radar.

Dropping siox/for-next is fine for me as well.  I assume siox patches
will still be picked up by Greg.

> Best regards
> Uwe

Best regards
Thorsten

linux-next: trees being removed

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1603 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)
----			----------------
arc			2023-09-10 16:28:41 -0700
  git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc.git#for-next
file-locks		2023-09-01 08:09:48 -0700
  git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git#locks-next
fsi			2023-12-14 19:44:11 +1030
  git://git.kernel.org/pub/scm/linux/kernel/git/joel/fsi.git#next
  ec084e4ec314 ("fsi: sbefifo: Bump up user write cmd length")
  f7236a0c919e ("fsi: sbefifo: Handle pending write command")
  c5eeb63edac9 ("fsi: Fix panic on scom file read")
gpio			2023-09-10 16:28:41 -0700
  git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git#for-next
header_cleanup		2024-01-15 15:52:12 -0500
  git://evilpiepirate.org/bcachefs.git#header_cleanup
kspp-gustavo		2024-01-21 14:11:32 -0800
  git://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux.git#for-next/kspp
tsm			2023-10-19 18:12:00 -0700
  git://git.kernel.org/pub/scm/linux/kernel/git/djbw/linux#tsm-next
zstd			2023-11-20 14:49:34 -0800
  https://github.com/terrelln/linux.git#zstd-next
  98988fc8e9ed ("zstd: import upstream v1.5.5")
  40eb0e915deb ("zstd: Backport Huffman speed improvement from upstream")
  3f832dfb8a8e ("zstd: fix g_debuglevel export warning")
zstd-fixes		2023-11-14 17:12:52 -0800
  https://github.com/terrelln/linux.git#zstd-linus

-- 
Cheers,
Stephen Rothwell

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

Re: linux-next: trees being removed

[Vineet Gupta]

On 2/12/25 04:26, 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)
> ----			----------------
> arc			2023-09-10 16:28:41 -0700
>   git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc.git#for-next

Ack: We don't need 2 next tending trees for ARC any longer.

Cheers,
-Vineet

> file-locks		2023-09-01 08:09:48 -0700
>   git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git#locks-next
> fsi			2023-12-14 19:44:11 +1030
>   git://git.kernel.org/pub/scm/linux/kernel/git/joel/fsi.git#next
>   ec084e4ec314 ("fsi: sbefifo: Bump up user write cmd length")
>   f7236a0c919e ("fsi: sbefifo: Handle pending write command")
>   c5eeb63edac9 ("fsi: Fix panic on scom file read")
> gpio			2023-09-10 16:28:41 -0700
>   git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git#for-next
> header_cleanup		2024-01-15 15:52:12 -0500
>   git://evilpiepirate.org/bcachefs.git#header_cleanup
> kspp-gustavo		2024-01-21 14:11:32 -0800
>   git://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux.git#for-next/kspp
> tsm			2023-10-19 18:12:00 -0700
>   git://git.kernel.org/pub/scm/linux/kernel/git/djbw/linux#tsm-next
> zstd			2023-11-20 14:49:34 -0800
>   https://github.com/terrelln/linux.git#zstd-next
>   98988fc8e9ed ("zstd: import upstream v1.5.5")
>   40eb0e915deb ("zstd: Backport Huffman speed improvement from upstream")
>   3f832dfb8a8e ("zstd: fix g_debuglevel export warning")
> zstd-fixes		2023-11-14 17:12:52 -0800
>   https://github.com/terrelln/linux.git#zstd-linus
>

Re: linux-next: trees being removed

[Stephen Rothwell]

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

Hi Vineet,

On Wed, 12 Feb 2025 22:02:09 +0530 Vineet Gupta <vgupta@kernel.org> wrote:
>
> On 2/12/25 04:26, 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)
> > ----			----------------
> > arc			2023-09-10 16:28:41 -0700
> >   git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc.git#for-next  
> 
> Ack: We don't need 2 next tending trees for ARC any longer.

This is supposed to be the development tree.  The only other one I have
is arc-current
(git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc.git#for-curr)
which is for bug fixes.  So do you really not do any development any more?

-- 
Cheers,
Stephen Rothwell

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

Re: linux-next: trees being removed

[Vineet Gupta]

On 2/16/25 03:11, Stephen Rothwell wrote:
> Hi Vineet,
>
> On Wed, 12 Feb 2025 22:02:09 +0530 Vineet Gupta <vgupta@kernel.org> wrote:
>> On 2/12/25 04:26, 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)
>>> ----			----------------
>>> arc			2023-09-10 16:28:41 -0700
>>>   git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc.git#for-next  
>> Ack: We don't need 2 next tending trees for ARC any longer.
> This is supposed to be the development tree.  The only other one I have
> is arc-current
> (git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc.git#for-curr)
> which is for bug fixes.  So do you really not do any development any more?

For quite some time I've been using just # for-curr for both fixes/features, as
dev as slowed down.
Things might change if and when work picks up on ARCv3/arc64 bit for now
for-curr suffices.

Thx,
-Vineet

Re: linux-next: trees being removed

[Stephen Rothwell]

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

Hi Vineet,

On Wed, 19 Feb 2025 11:58:58 -0800 Vineet Gupta <vgupta@kernel.org> wrote:
>
> For quite some time I've been using just # for-curr for both fixes/features, as
> dev as slowed down.
> Things might change if and when work picks up on ARCv3/arc64 bit for now
> for-curr suffices.

OK, I have removed the arc tree from today.

-- 
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: 1676 bytes --]

Hi all,

On Wed, 12 Feb 2025 09:56:32 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Tree			Last commit date
>   URL
>   comits (if any)
> ----			----------------
> file-locks		2023-09-01 08:09:48 -0700
>   git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git#locks-next
> fsi			2023-12-14 19:44:11 +1030
>   git://git.kernel.org/pub/scm/linux/kernel/git/joel/fsi.git#next
>   ec084e4ec314 ("fsi: sbefifo: Bump up user write cmd length")
>   f7236a0c919e ("fsi: sbefifo: Handle pending write command")
>   c5eeb63edac9 ("fsi: Fix panic on scom file read")
> gpio			2023-09-10 16:28:41 -0700
>   git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git#for-next
> header_cleanup		2024-01-15 15:52:12 -0500
>   git://evilpiepirate.org/bcachefs.git#header_cleanup
> kspp-gustavo		2024-01-21 14:11:32 -0800
>   git://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux.git#for-next/kspp
> tsm			2023-10-19 18:12:00 -0700
>   git://git.kernel.org/pub/scm/linux/kernel/git/djbw/linux#tsm-next
> zstd			2023-11-20 14:49:34 -0800
>   https://github.com/terrelln/linux.git#zstd-next
>   98988fc8e9ed ("zstd: import upstream v1.5.5")
>   40eb0e915deb ("zstd: Backport Huffman speed improvement from upstream")
>   3f832dfb8a8e ("zstd: fix g_debuglevel export warning")
> zstd-fixes		2023-11-14 17:12:52 -0800
>   https://github.com/terrelln/linux.git#zstd-linus

All the above trees have been removed.  Give me a yell if you want one
back.

> arc			2023-09-10 16:28:41 -0700
>   git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc.git#for-next

This one is still pending.

-- 
Cheers,
Stephen Rothwell

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

Re: linux-next: trees being removed

[Nick Terrell]

Hi Stephen,

> On Feb 16, 2025, at 6:42 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> Hi all,
> 
> On Wed, 12 Feb 2025 09:56:32 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>> 
>> Tree Last commit date
>>  URL
>>  comits (if any)
>> ---- ----------------
>> file-locks 2023-09-01 08:09:48 -0700
>>  git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git#locks-next
>> fsi 2023-12-14 19:44:11 +1030
>>  git://git.kernel.org/pub/scm/linux/kernel/git/joel/fsi.git#next
>>  ec084e4ec314 ("fsi: sbefifo: Bump up user write cmd length")
>>  f7236a0c919e ("fsi: sbefifo: Handle pending write command")
>>  c5eeb63edac9 ("fsi: Fix panic on scom file read")
>> gpio 2023-09-10 16:28:41 -0700
>>  git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git#for-next
>> header_cleanup 2024-01-15 15:52:12 -0500
>>  git://evilpiepirate.org/bcachefs.git#header_cleanup
>> kspp-gustavo 2024-01-21 14:11:32 -0800
>>  git://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux.git#for-next/kspp
>> tsm 2023-10-19 18:12:00 -0700
>>  git://git.kernel.org/pub/scm/linux/kernel/git/djbw/linux#tsm-next
>> zstd 2023-11-20 14:49:34 -0800
>>  https://github.com/terrelln/linux.git#zstd-next

Could I get the (`zstd`, `https://github.com/terrelln/linux.git#zstd-next`) tree back please?

We just released zstd-1.5.7 upstream, and I'm working on updating the kernel to this
version. David Sterba alerted me to this [1].

Thanks & sorry for the churn,
Nick Terrell

[1] https://github.com/facebook/zstd/issues/4262

>>  98988fc8e9ed ("zstd: import upstream v1.5.5")
>>  40eb0e915deb ("zstd: Backport Huffman speed improvement from upstream")
>>  3f832dfb8a8e ("zstd: fix g_debuglevel export warning")
>> zstd-fixes 2023-11-14 17:12:52 -0800
>>  https://github.com/terrelln/linux.git#zstd-linus
> 
> All the above trees have been removed.  Give me a yell if you want one
> back.
> 
>> arc 2023-09-10 16:28:41 -0700
>>  git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc.git#for-next
> 
> This one is still pending.
> 
> -- 
> Cheers,
> Stephen Rothwell

Re: linux-next: trees being removed

[Stephen Rothwell]

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

Hi Nick,

On Wed, 5 Mar 2025 21:34:18 +0000 Nick Terrell <terrelln@meta.com> wrote:
>
> > On Wed, 12 Feb 2025 09:56:32 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:  
> >> 
> >> Tree Last commit date
> >>  URL
> >>  comits (if any)
> >> ---- ----------------
> >> zstd 2023-11-20 14:49:34 -0800
> >>  https://github.com/terrelln/linux.git#zstd-next  
> 
> Could I get the (`zstd`, `https://github.com/terrelln/linux.git#zstd-next`) tree back please?
> 
> We just released zstd-1.5.7 upstream, and I'm working on updating the kernel to this
> version. David Sterba alerted me to this [1].
> 
> Thanks & sorry for the churn,

No worries, it is back from today.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgement of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
        Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

-- 
Cheers,
Stephen Rothwell 
sfr@canb.auug.org.au

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

linux-next: trees being removed

[Stephen Rothwell]

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

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 (or
later restored), just let me know (and update its branch).

Tree			Last commit date
  URL
  comits (if any)
----			----------------
cfi			2023-07-09 13:53:13 -0700
  git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git#cfi/next
djw-vfs			2023-08-04 08:20:57 -0700
  git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git#vfs-for-next
drm-tegra		2023-04-06 14:02:33 +0200
  https://gitlab.freedesktop.org/drm/tegra.git#for-next
mux			2023-05-21 14:05:48 -0700
  https://gitlab.com/peda-linux/mux.git#for-next
pidfd			2023-07-02 11:14:54 -0700
  git://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux.git#for-next
soc-fsl			2023-06-08 17:56:26 -0500
  git://git.kernel.org/pub/scm/linux/kernel/git/leo/linux.git#next
soc-fsl-fixes		2023-07-09 13:53:13 -0700
  git://git.kernel.org/pub/scm/linux/kernel/git/leo/linux.git#fix
uml-fixes		2023-05-10 00:21:30 +0200
  git://git.kernel.org/pub/scm/linux/kernel/git/uml/linux.git#fixes

-- 
Cheers,
Stephen Rothwell

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

Re: linux-next: trees being removed

[Peter Rosin]

Hi!

2024-08-13 at 00:51, 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 (or
> later restored), just let me know (and update its branch).
> 
> Tree			Last commit date
>   URL
>   comits (if any)
> ----			----------------
> cfi			2023-07-09 13:53:13 -0700
>   git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git#cfi/next
> djw-vfs			2023-08-04 08:20:57 -0700
>   git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git#vfs-for-next
> drm-tegra		2023-04-06 14:02:33 +0200
>   https://gitlab.freedesktop.org/drm/tegra.git#for-next
> mux			2023-05-21 14:05:48 -0700
>   https://gitlab.com/peda-linux/mux.git#for-next
> pidfd			2023-07-02 11:14:54 -0700
>   git://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux.git#for-next
> soc-fsl			2023-06-08 17:56:26 -0500
>   git://git.kernel.org/pub/scm/linux/kernel/git/leo/linux.git#next
> soc-fsl-fixes		2023-07-09 13:53:13 -0700
>   git://git.kernel.org/pub/scm/linux/kernel/git/leo/linux.git#fix
> uml-fixes		2023-05-10 00:21:30 +0200
>   git://git.kernel.org/pub/scm/linux/kernel/git/uml/linux.git#fixes
> 

Could you please keep the mux tree for a while? I have been very busy
lately and not much is going on, but I would still like to be able to
get things into -next. I guess I could just ask to include it again
when I need it, but...

Cheers,
Peter

Re: linux-next: trees being removed

[Stephen Rothwell]

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

Hi Peter,

On Tue, 13 Aug 2024 07:13:08 +0200 Peter Rosin <peda@axentia.se> wrote:
>
> > mux			2023-05-21 14:05:48 -0700
> >   https://gitlab.com/peda-linux/mux.git#for-next
> 
> Could you please keep the mux tree for a while? I have been very busy
> lately and not much is going on, but I would still like to be able to
> get things into -next. I guess I could just ask to include it again
> when I need it, but...

No worries, I will keep it in.  You might consider fast forwarding your
for-next branch to v6.10 or v6.11-rc1 (or something else recent), then
I won't forget this email and ask you again in a few months.  :-)

-- 
Cheers,
Stephen Rothwell

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

Re: linux-next: trees being removed

[Vignesh Raghavendra]

Hi Stephen

On 13/08/24 04:21, 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 (or
> later restored), just let me know (and update its branch).
> 
> Tree			Last commit date
>   URL
>   comits (if any)
> ----			----------------
> cfi			2023-07-09 13:53:13 -0700
>   git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git#cfi/next


Could you please keep this branch included for a while? I expect active
contributions (although will just be handful of patches) here.

I will remember to keep this updated to latest rc when there isn't any
new things to queue for a window. Thanks!

-- 
Regards
Vignesh

Re: linux-next: trees being removed

[Stephen Rothwell]

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

Hi Vignesh,

On Wed, 14 Aug 2024 15:36:44 +0530 Vignesh Raghavendra <vigneshr@ti.com> wrote:
>
> On 13/08/24 04:21, Stephen Rothwell wrote:
> > 
> > cfi			2023-07-09 13:53:13 -0700
> >   git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git#cfi/next  
> 
> 
> Could you please keep this branch included for a while? I expect active
> contributions (although will just be handful of patches) here.
> 
> I will remember to keep this updated to latest rc when there isn't any
> new things to queue for a window. Thanks!

No problem.  I will keep it.

-- 
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: 1142 bytes --]

Hi all,

On Tue, 13 Aug 2024 08:51:47 +1000 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 kept (or
> later restored), just let me know (and update its branch).
> 
> Tree			Last commit date
>   URL
>   comits (if any)
> ----			----------------
> djw-vfs			2023-08-04 08:20:57 -0700
>   git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git#vfs-for-next
> drm-tegra		2023-04-06 14:02:33 +0200
>   https://gitlab.freedesktop.org/drm/tegra.git#for-next
> pidfd			2023-07-02 11:14:54 -0700
>   git://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux.git#for-next
> soc-fsl			2023-06-08 17:56:26 -0500
>   git://git.kernel.org/pub/scm/linux/kernel/git/leo/linux.git#next
> soc-fsl-fixes		2023-07-09 13:53:13 -0700
>   git://git.kernel.org/pub/scm/linux/kernel/git/leo/linux.git#fix
> uml-fixes		2023-05-10 00:21:30 +0200
>   git://git.kernel.org/pub/scm/linux/kernel/git/uml/linux.git#fixes

The above trees have now been removed from linux-next.
-- 
Cheers,
Stephen Rothwell

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

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

[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

[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: 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 --]