[Kernel-packages] [Bug 1882088] Comment bridged from LTC Bugzilla

2020-07-10 Thread bugproxy
--- Comment From stefan.ra...@de.ibm.com 2020-07-10 11:24 EDT--- Here is a proper link: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=fb4f79264c0fc6fd5a68ffe3e31bfff97311e1f1 -- You received this bug notification because you are a member of Kernel Packages,

[Kernel-packages] [Bug 1882088] Comment bridged from LTC Bugzilla

2020-07-09 Thread bugproxy
--- Comment From stefan.ra...@de.ibm.com 2020-07-09 07:02 EDT--- The patch was posted upstream, see https://www.spinics.net/lists/netdev/msg666808.html, and accepted by Dave Miller. I just checked his net-next tree, didn't see it there yet, but I would assume it will appear there soon.

[Kernel-packages] [Bug 1882088] Comment bridged from LTC Bugzilla

2020-06-29 Thread bugproxy
--- Comment From stefan.ra...@de.ibm.com 2020-06-29 08:07 EDT--- As I wrote in a previous comment, it's not so much a question 'if' we can post it upstream, but rather 'at which time': We assume that we get a lot of resistance upstream if we post any code for v2 in absence of an RFC

[Kernel-packages] [Bug 1882088] Comment bridged from LTC Bugzilla

2020-06-04 Thread bugproxy
--- Comment From stefan.ra...@de.ibm.com 2020-06-04 11:02 EDT--- That's a very valid question. The problem is that we cannot talk about v2 yet for legal reasons. We're pending some internal processing and especially a new RFC on v2. We assume that we get a lot of resistance upstream if

[Kernel-packages] [Bug 1882088] Comment bridged from LTC Bugzilla

2020-06-04 Thread bugproxy
--- Comment From stefan.ra...@de.ibm.com 2020-06-04 10:10 EDT--- Note: This patch is currently not upstream. It will be part of the full SMC-D v2 implementation (see LP1853291), and was successfully tested with a reference implementation. However, we still have some way to go with our