net-next is CLOSED

net-next is CLOSED

[Jakub Kicinski]

It's a wrap, please stop sending -next material.

As most of you know from Twitter Dave had a medical emergency 
and we're temporarily on our own :(

I may not be able to flip the "net-next" image on vger, so please 
just watch the mailing list for an announcement when tree opens.

Re: net-next is CLOSED

[Jiri Pirko]

Mon, Feb 20, 2023 at 07:56:34AM CET, pabeni@redhat.com wrote:
>Hi!
>
>Linus has tagged v6.2, so please defer posting new features,
>re-factoring etc. until the 6.3 merge window is over.
>
>As usual, feel free sharing RFC for such topics even in the merge
>window.

Who is flipping http://vger.kernel.org/~davem/net-next.html ?
It's still "open" there.


>
>Thanks,
>
>Paolo
>
>
>

net-next is CLOSED

[Paolo Abeni]

Hi!

Linus has tagged v6.2, so please defer posting new features,
re-factoring etc. until the 6.3 merge window is over.

As usual, feel free sharing RFC for such topics even in the merge
window.

Thanks,

Paolo

net-next is CLOSED

[Jakub Kicinski]

Hi,

as is tradition, net-next is closed for the duration 
of the merge window.

net-next is CLOSED

[Jakub Kicinski]

Hi!

Linus has tagged v6.0, so please defer posting new features,
re-factoring etc. until the 6.1 merge window is over.


BTW we're always open to feedback about the process, if you think
the merge window closure is counter-productive - please LMK.
I asked around some time ago and the answers ranged from
"don't care" to "closures are useful".

net-next is closed

[Jakub Kicinski]

Hi everyone!

Linus has cut the 5.19 release. We'll look thru what's already in 
the patchwork queue and take upstream PRs but please hold off on
(non-RFC) net-next patches until the merge window is over.

Thanks!

net-next is closed

[Jakub Kicinski]

Hi everyone!

Linus has cut the 5.18 release. We'll look thru what's already in
patchwork tomorrow and take remaining sub-tree PRs but any patches 
applied directly to the netdev trees should be fixes only from now
until the merge window is over.

Thanks!

net-next is closed

[Jakub Kicinski]

Hi everyone!

Linus has cut the 5.17 release. We'd like to allow a day or two 
to resolve known issues in net-next before sending a PR but please
consider net-next to be closed already. We'll be taking fixes only.

Thanks!

Re: net-next is CLOSED

[Jakub Kicinski]

On Wed, 16 Dec 2020 18:42:47 +0200 Vladimir Oltean wrote:
> On Tue, Dec 15, 2020 at 09:10:56AM -0800, Jakub Kicinski wrote:
> > The 5.10 PR went out yesterday, you know the drill.
> >
> > There are a few things (Vladimir's DSA+non-DSA bridging series, mlx5 SF
> > patches, Intel's S0ix fixes, Octeon multi-group RSS, threaded NAPI)
> > which we may include in the Thu PR if there is enough confidence.
> > Any other new feature should be posted as RFC at this point.  
> 
> First of all, congratulations for surviving this kernel development
> cycle :D you did a great job and spent a lot of time reviewing code.

Thanks, it's a team effort, so good job everyone! :)

> From my side there is absolutely zero urgency to send another pull
> request with the DSA features that did not make it in time for the first
> PR. I am happy to resend whenever net-next reopens.

Perfect, thanks for the clarification!

Re: net-next is CLOSED

[Vladimir Oltean]

Hi Jakub,

On Tue, Dec 15, 2020 at 09:10:56AM -0800, Jakub Kicinski wrote:
> The 5.10 PR went out yesterday, you know the drill.
>
> There are a few things (Vladimir's DSA+non-DSA bridging series, mlx5 SF
> patches, Intel's S0ix fixes, Octeon multi-group RSS, threaded NAPI)
> which we may include in the Thu PR if there is enough confidence.
> Any other new feature should be posted as RFC at this point.

First of all, congratulations for surviving this kernel development
cycle :D you did a great job and spent a lot of time reviewing code.

From my side there is absolutely zero urgency to send another pull
request with the DSA features that did not make it in time for the first
PR. I am happy to resend whenever net-next reopens.

Thanks,
-Vladimir

net-next is CLOSED

[Jakub Kicinski]

The 5.10 PR went out yesterday, you know the drill.

There are a few things (Vladimir's DSA+non-DSA bridging series, mlx5 SF
patches, Intel's S0ix fixes, Octeon multi-group RSS, threaded NAPI)
which we may include in the Thu PR if there is enough confidence.
Any other new feature should be posted as RFC at this point.


Thanks!

net-next is CLOSED

[David Miller]

Bug fixes only now, thank you.

net-next is CLOSED

[David Miller]

The net-next tree is CLOSED, submit bug fixes only at this time.

Alexei has told me that the bpf-next pull request is pending and
I will take that in when I get it from him.

Thanks.

net-next is CLOSED

[David Miller]

Bug fixes only at this time, thank you.

net-next is CLOSED

[David Miller]

You all know the drill:

	http://vger.kernel.org/~davem/net-next.html

Kinda not impressed with all of the panic submissions after v5.5-final
got released.  But, what can I do :-/

Bug fixes only now, thank you.

net-next is CLOSED

[David Miller]

If it's not in patchwork right now it will miss the merge window this
time around, don't try to sneak things in, thank you.

	http://vger.kernel.org/~davem/net-next.html

Bug fixes only please.

net-next is CLOSED...

[David Miller]

It's merge window time...

net-next is CLOSED

[David Miller]

Ok that's enough, gotta close the door... :-)

Please bug fixes only at this point, thank you.

net-next is CLOSED

[David Miller]

Don't even think about submitting anything other than bug fixes :-)

Thank you.

net-next is CLOSED

[David Miller]

Please only bug fixes as we progress through the merge window.

I'll announce when net-next is open again.

Follow me on social media:

https://twitter.com/davem_dokebi

Thank you.

Re: net-next is CLOSED

[David Miller]

From: Saeed Mahameed <saeedm@mellanox.com>
Date: Fri, 21 Dec 2018 07:37:29 +0000

> On Thu, 2018-12-20 at 23:15 -0800, David Miller wrote:
>> Please keep it to bug fixes.
>> 
>> Thank you for your cooperation.
> 
> What happens to a series that i sent 10 minutes before this email, but
> for some reason it still doesn't show up in the mailing list ?
> 
> I really would like for that series to make it through, i think you
> will personally like it :).

Ok since there was a true race condition, I've pulled :-)

Re: net-next is CLOSED

[Saeed Mahameed]

On Thu, 2018-12-20 at 23:15 -0800, David Miller wrote:
> Please keep it to bug fixes.
> 
> Thank you for your cooperation.

What happens to a series that i sent 10 minutes before this email, but
for some reason it still doesn't show up in the mailing list ?

I really would like for that series to make it through, i think you
will personally like it :).

Thanks,
Saeed.

net-next is CLOSED

[David Miller]

Please keep it to bug fixes.

Thank you for your cooperation.

net-next is CLOSED

[David Miller]

Please do not submit net-next changes until that tree opens back
up again after the merge window.

Thank you.

net-next is CLOSED...

[David Miller]

Please only submit bug fixes at this time, thank you.

net-next is CLOSED

[David Miller]

I only expect a bpf-next pull request from Alexei and Daniel at
this point.

Thank you.

net-next is CLOSED...

[David Miller]

With the release of 4.15 final, the net-next tree is close.

Please do not try to submit cleanups or new features at this time, I
will immediately toss them from patchwork.

Work on fixing bugs instead :-)

net-next is CLOSED

[David Miller]

If it isn't a bug fix and it isn't in patchwork right now, I don't
want to see it.

This time around inappropriate submissions will be silently marked
as "deferred" in patchwork and not even looked at by me.

Thanks.

net-next is CLOSED

[David Miller]

Please do not submit anything other than bug fixes from
this point forward, thank you.

I should be sending a net-next pull request to Linus today
or tomorrow.

Thanks.

Re: net-next is CLOSED

[David Miller]

From: Johannes Berg <johannes@sipsolutions.net>
Date: Tue, 12 Jan 2016 10:55:08 +0100

> On Sun, 2016-01-10 at 22:04 -0500, David Miller wrote:
>> The merge window has just openned, which means that no new
>> submissions for net-next should be made at this time.
>> 
> 
> I had a submission before, but perhaps due to my UTF-8 problem
> patchwork didn't pick it up and you missed it. Sorry.

Please just resubmit, thanks.

Re: net-next is CLOSED

[Johannes Berg]

On Sun, 2016-01-10 at 22:04 -0500, David Miller wrote:
> The merge window has just openned, which means that no new
> submissions for net-next should be made at this time.
> 

I had a submission before, but perhaps due to my UTF-8 problem
patchwork didn't pick it up and you missed it. Sorry.

Let me know if you're planning to pick it up still - if not I'll rebase
to split it up more properly.

Thanks,
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

net-next is CLOSED

[David Miller]

The merge window has just openned, which means that no new submissions
for net-next should be made at this time.

Thanks in advance for your cooperation, and can we _PLEASE_ have one
release cycle where everyone tries hard not to submit any net-next
material during this closed time period?  It'll make my life 10 times
easier.

net-next is CLOSED...

[David Miller]

We are in a sort-of state of limbo with 3.17 having been released the
other day and the actual merge window integration happening next week
when Linus returns from some travels.

Please do not submit new feature patches until I open net-next back
up which will probably be in just over 2 weeks from now.

I understand that the ->xmit_more batching stuff might still need
some fixes and/or heuristic tweaks and that's fine.

Please direct your efforts to stabilizing things over the next
week or two, thanks!

net-next is CLOSED

[David Miller]

The merge window has openned up and I have just emptied the backlog
of patches in patchwork.

This means only bug fixes from this point forward until I indicate
that net-next is open again.

Any patches submitted for net-next beforehand will be tossed from
patchwork, and must be resubmitted at the proper time when net-next is
open again.

Thanks.