Conversation
kernellogger@fosstodon.org

Thorsten Leemhuis (acct. 1/4)

Edited 4 months ago

No -next today or in the next two weeks from Stephen:

https://lore.kernel.org/all/20240613144524.22abd1a0@canb.auug.org.au/

[Update]
@broonie will "provide backup coverage" during that time (see replies for details).
[/Update]

1
1
0
z3ntu@fosstodon.org

Luca Weiss

Reply to @kernellogger@fosstodon.org

@kernellogger Makes me question if it's a good idea to let one person be responsible for maintaining this tree while it's often meant to be used for basing your new changes on to not conflict with other changes that will be merged.
And I think also for (automated) testing it's very commonly used.

2
0
0
kernellogger@fosstodon.org

Thorsten Leemhuis (acct. 1/4)

Reply to @z3ntu@fosstodon.org
Edited 4 months ago

@z3ntu

There were times when somebody else stepped in. Not sure if that will be the case here (I assume otherwise Stephen would have mentioned this).

But well, that's how it is with the kernel, as it's development ist not driven by some "foundation"[1] that hires people to do task like this (for docs, bug triaging, and a few other things this is a problem as well).

[1] but those have downsides, too!

1
0
0
gregkh

Greg K-H

Reply to @kernellogger@fosstodon.org
@kernellogger @z3ntu Please note that the employer of the linux-next maintainer graciously allows them to do this work on company time because they value it. Perhaps other companies should also allow their developers to help out with this (note, at least one does, so Stephen isn't always alone here)

And we are allowed, and in some places, required, to go on vacation, so a few weeks off isn't going to really stall anything, we all have other ways of testing integrations, so don't worry :)
1
7
18
broonie@mastodon.social

broonie

Reply to @z3ntu@fosstodon.org

@z3ntu @kernellogger I provide backup coverage, Stephen doesn’t like assuming that I’m always available or pressuring me into it and just announces his vacation with no assumption that anything will happen.

1
0
1
broonie@mastodon.social

broonie

Reply to @gregkh

@gregkh @kernellogger @z3ntu Yup, when I provide cover it’s work time and I borrow a big aarch64 build machine we have to do the actual builds.

0
0
1
kernellogger@fosstodon.org

Thorsten Leemhuis (acct. 1/4)

Reply to @broonie@mastodon.social

@broonie @z3ntu

ahh, great, many thx for that (to your employer, too), much appreciated (regression tracking benefits from -next, too, as is easier when it is available)

0
0
0
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: