Discussion:
Can we have 3.16 branch for 13.2?
(too old to reply)
Stephan Kulow
2014-10-10 08:34:28 UTC
Permalink
Raw Message
Hi,

3.17 is now submitted to Factory and that's all fine. But for 13.2
I would like to stick with what is in RC1 + fixes. Can we have a branch
for that?

Greetings, Stephan
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe-***@public.gmane.org
To contact the owner, e-mail: opensuse-kernel+owner-***@public.gmane.org
Jiri Slaby
2014-10-10 09:09:44 UTC
Permalink
Raw Message
Post by Stephan Kulow
Hi,
3.17 is now submitted to Factory and that's all fine. But for 13.2
I would like to stick with what is in RC1 + fixes. Can we have a branch
for that?
Hi, openSUSE:13.2 is now in the repo with 3.16.5.

Are you sure, you want 3.16 in 13.2? It has the ugly timeout bug in it
which is fixed only in 3.17. (bnc#891645)
--
js
suse labs
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe-***@public.gmane.org
To contact the owner, e-mail: opensuse-kernel+owner-***@public.gmane.org
Stephan Kulow
2014-10-10 09:14:01 UTC
Permalink
Raw Message
Post by Jiri Slaby
Post by Stephan Kulow
Hi,
3.17 is now submitted to Factory and that's all fine. But for 13.2
I would like to stick with what is in RC1 + fixes. Can we have a branch
for that?
Hi, openSUSE:13.2 is now in the repo with 3.16.5.
Are you sure, you want 3.16 in 13.2? It has the ugly timeout bug in it
which is fixed only in 3.17. (bnc#891645)
I'm more worried about things 3.17 breaks than things it fixes - perhaps
we can work on a 3.17 maintenance update to see?

Greetings, Stephan
David Sterba
2014-10-10 09:43:48 UTC
Permalink
Raw Message
Post by Stephan Kulow
Post by Jiri Slaby
Post by Stephan Kulow
Hi,
3.17 is now submitted to Factory and that's all fine. But for 13.2
I would like to stick with what is in RC1 + fixes. Can we have a branch
for that?
Hi, openSUSE:13.2 is now in the repo with 3.16.5.
Are you sure, you want 3.16 in 13.2? It has the ugly timeout bug in it
which is fixed only in 3.17. (bnc#891645)
I'm more worried about things 3.17 breaks than things it fixes - perhaps
we can work on a 3.17 maintenance update to see?
I agree about keeping 3.16 for now, 3.17 is still too fresh and not
suitable for switch in RC1 phase.
Jeff Mahoney
2014-10-10 14:09:58 UTC
Permalink
Raw Message
Post by David Sterba
Post by Stephan Kulow
Post by Jiri Slaby
Post by Stephan Kulow
Hi,
3.17 is now submitted to Factory and that's all fine. But for
13.2 I would like to stick with what is in RC1 + fixes. Can
we have a branch for that?
Hi, openSUSE:13.2 is now in the repo with 3.16.5.
Are you sure, you want 3.16 in 13.2? It has the ugly timeout
bug in it which is fixed only in 3.17. (bnc#891645)
I'm more worried about things 3.17 breaks than things it fixes -
perhaps we can work on a 3.17 maintenance update to see?
I agree about keeping 3.16 for now, 3.17 is still too fresh and
not suitable for switch in RC1 phase.
Yeah, I assumed we'd use 3.16 as well since RC1 was supposed to be
yesterday. I'll create a openSUSE-13.2 branch from the stable branch
that we can use.

- -Jeff

- --
Jeff Mahoney
SUSE Labs
Jeff Mahoney
2014-10-10 14:12:34 UTC
Permalink
Raw Message
Post by Jeff Mahoney
Post by David Sterba
Post by Stephan Kulow
Post by Jiri Slaby
Post by Stephan Kulow
Hi,
3.17 is now submitted to Factory and that's all fine. But
for 13.2 I would like to stick with what is in RC1 + fixes.
Can we have a branch for that?
Hi, openSUSE:13.2 is now in the repo with 3.16.5.
Are you sure, you want 3.16 in 13.2? It has the ugly timeout
bug in it which is fixed only in 3.17. (bnc#891645)
I'm more worried about things 3.17 breaks than things it fixes
- perhaps we can work on a 3.17 maintenance update to see?
I agree about keeping 3.16 for now, 3.17 is still too fresh and
not suitable for switch in RC1 phase.
Yeah, I assumed we'd use 3.16 as well since RC1 was supposed to be
yesterday. I'll create a openSUSE-13.2 branch from the stable
branch that we can use.
Oops. Looks like Jiri beat me to it. :)

- -Jeff

- --
Jeff Mahoney
SUSE Labs
Jiri Slaby
2014-10-13 08:14:34 UTC
Permalink
Raw Message
Post by Jeff Mahoney
Post by Jeff Mahoney
Post by Jiri Slaby
Post by Stephan Kulow
Hi,
3.17 is now submitted to Factory and that's all fine.
But for 13.2 I would like to stick with what is in RC1 +
fixes. Can we have a branch for that?
Hi, openSUSE:13.2 is now in the repo with 3.16.5.
Yeah, I assumed we'd use 3.16 as well since RC1 was supposed to
be yesterday. I'll create a openSUSE-13.2 branch from the stable
branch that we can use.
Oops. Looks like Jiri beat me to it. :)
Yet, Michal, could you set up the machinery at OBS' Kernel:*?

thanks,
- --
js
suse labs
Michal Marek
2014-10-13 08:59:50 UTC
Permalink
Raw Message
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Post by Jeff Mahoney
Post by Jeff Mahoney
Yeah, I assumed we'd use 3.16 as well since RC1 was supposed to
be yesterday. I'll create a openSUSE-13.2 branch from the stable
branch that we can use.
Oops. Looks like Jiri beat me to it. :)
Yet, Michal, could you set up the machinery at OBS' Kernel:*?
I added openSUSE-13.2 to the config at
http://kerncvs.suse.de/gitweb/?p=kbuild.git;a=blob;f=branches.conf;hb=HEAD
(internal only).

Michal
Matwey V. Kornilov
2014-10-13 18:57:07 UTC
Permalink
Raw Message
Post by Michal Marek
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Post by Jeff Mahoney
Post by Jeff Mahoney
Yeah, I assumed we'd use 3.16 as well since RC1 was supposed to
be yesterday. I'll create a openSUSE-13.2 branch from the stable
branch that we can use.
Oops. Looks like Jiri beat me to it. :)
Yet, Michal, could you set up the machinery at OBS' Kernel:*?
I added openSUSE-13.2 to the config at
http://kerncvs.suse.de/gitweb/?p=kbuild.git;a=blob;f=branches.conf;hb=HEAD
(internal only).
Michal
Hi,

I see openSUSE-13.2 on kernel.opensuse.org but don't see appropriate
project Kernel:openSUSE-13.2 on build.opensuse.org
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe-***@public.gmane.org
To contact the owner, e-mail: opensuse-kernel+owner-***@public.gmane.org
Michal Marek
2014-10-14 20:01:05 UTC
Permalink
Raw Message
Post by Matwey V. Kornilov
Post by Michal Marek
I added openSUSE-13.2 to the config at
http://kerncvs.suse.de/gitweb/?p=kbuild.git;a=blob;f=branches.conf;hb=HEAD
(internal only).
I see openSUSE-13.2 on kernel.opensuse.org but don't see appropriate
project Kernel:openSUSE-13.2 on build.opensuse.org
The Kernel:* projects are updated each day at 8:00 CET, so you were
checking too early.

Michal
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe-***@public.gmane.org
To contact the owner, e-mail: opensuse-kernel+owner-***@public.gmane.org
Matwey V. Kornilov
2014-10-15 15:09:49 UTC
Permalink
Raw Message
Post by Michal Marek
Post by Matwey V. Kornilov
Post by Michal Marek
I added openSUSE-13.2 to the config at
http://kerncvs.suse.de/gitweb/?p=kbuild.git;a=blob;f=branches.conf;hb=HEAD
(internal only).
I see openSUSE-13.2 on kernel.opensuse.org but don't see appropriate
project Kernel:openSUSE-13.2 on build.opensuse.org
The Kernel:* projects are updated each day at 8:00 CET, so you were
checking too early.
Michal
Now It is here, thank you
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe-***@public.gmane.org
To contact the owner, e-mail: opensuse-kernel+owner-***@public.gmane.org
Stephan Kulow
2014-10-10 17:04:55 UTC
Permalink
Raw Message
Post by Jiri Slaby
Post by Stephan Kulow
Hi,
3.17 is now submitted to Factory and that's all fine. But for 13.2
I would like to stick with what is in RC1 + fixes. Can we have a branch
for that?
Hi, openSUSE:13.2 is now in the repo with 3.16.5.
Are you sure, you want 3.16 in 13.2? It has the ugly timeout bug in it
which is fixed only in 3.17. (bnc#891645)
kernel 3.17 is problematic in staging anyway:
http://s.kulow.org/virtualbox-failure

Greetings, Stephan
--
Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die
ganze Welt an Arsch offen hat, oder grad deswegn.
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe-***@public.gmane.org
To contact the owner, e-mail: opensuse-kernel+owner-***@public.gmane.org
Michal Kubecek
2014-10-11 23:39:40 UTC
Permalink
Raw Message
Post by Stephan Kulow
http://s.kulow.org/virtualbox-failure
I wouldn't call that "kernel 3.17 is problematic", it's just a usual
need to adjust third-party drivers to API changes. I had to handle
exactly the same problem (alloc_netdev() having 4 arguments now) for
VMware host modules. Of course, both VMware and VirtualBox will provide
fixes in the end.

Michal Kubeček
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe-***@public.gmane.org
To contact the owner, e-mail: opensuse-kernel+owner-***@public.gmane.org
Larry Finger
2014-10-12 15:39:45 UTC
Permalink
Raw Message
Post by Michal Kubecek
Post by Stephan Kulow
http://s.kulow.org/virtualbox-failure
I wouldn't call that "kernel 3.17 is problematic", it's just a usual
need to adjust third-party drivers to API changes. I had to handle
exactly the same problem (alloc_netdev() having 4 arguments now) for
VMware host modules. Of course, both VMware and VirtualBox will provide
fixes in the end.
The failure that Stephan posted was for VB 4.3.14. Both 4.3.16 and 4.3.18 build
on kernels 3.17 and 3.18 (at least this far into the merge).

Larry
Stephan Kulow
2014-10-13 08:09:29 UTC
Permalink
Raw Message
Post by Larry Finger
Post by Michal Kubecek
Post by Stephan Kulow
http://s.kulow.org/virtualbox-failure
I wouldn't call that "kernel 3.17 is problematic", it's just a usual
need to adjust third-party drivers to API changes. I had to handle
exactly the same problem (alloc_netdev() having 4 arguments now) for
VMware host modules. Of course, both VMware and VirtualBox will provide
fixes in the end.
The failure that Stephan posted was for VB 4.3.14. Both 4.3.16 and
4.3.18 build on kernels 3.17 and 3.18 (at least this far into the merge).
That won't help unless someone submits an update to Virtualbox

Greetings, Stephan
Loading...