-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 3/16/15 12:37 PM, Alexander Graf wrote:
On 16.03.15 11:51, Jeff Mahoney wrote:
On 3/16/15 11:45 AM, Andreas Färber wrote:
Am 16.03.2015 um 16:29 schrieb Jeff Mahoney:
On 3/13/15 12:58 PM, Andreas Färber wrote:
Am 13.03.2015 um 17:52 schrieb Dirk Müller:
patches.arch/arm64-0008-adjust-to-kernel-4.0 | 34 ++++++++++++++++++++++++++++ It looks to me as if instead an earlier patch in that series should be updated?
What we'd prefer to see is patches that match upstream or, at the very least, patches that match a repository that is a maintainer branch leading to mainline inclusion[1]. This patchset has patches that just say things like "no" and "never" for Patch-mainline without any explanation as to why. It seems we need to be a bit more vigilant with our policy enforcement.
P.S. I always thought those arm64 patches were 13.2 only...
As opposed to the master branch or something else? I'd expect that anything in an older openSUSE release would still be supported in a newer one unless the hardware is going out of scope.
AFAIU agraf prepared a patchset to backport arm64 PCI/network for 13.2, so that people have a usable stable release for Mustang and Seattle with our 3.16 kernel. Makes sense to me.
So yes, I am surprised that non-mainline patches end up on master branch as opposed to just waiting until final patches trickle through maintainers' trees into linux.git and the next -rc or tarball.
For hardware enablement, I get it. If people have hardware in hand, it can be bothersome to wait for the wheels to turn. In that case, I want to see mailing list references for the patches. Even if we're the ones doing the development, the work should still be public enough that references are available.
It's complicated for the xgbe-a0 driver. That one was basically a downstream patch on top of the upstream b0 driver. AMD's idea was that nobody should eventually have a0 hardware in their hands once b0 silicon is out, so the driver wasn't worth pushing upstream.
I think we're still stuck keeping it alive downstream for a little while, but over time it will just disappear. Meanwhile we need it though to support the hardware we (and early adopters) have.
Ok, makes sense. This is exactly the sort of thing that should go in the patch/commit, though. :) - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) iQIcBAEBAgAGBQJVBxx5AAoJEB57S2MheeWyD8YP/RvlPnaHGw3X/kyYPyYR986u FRsqiPL0rGZfIEAGl6mudddAiq+YbRsYWPvDC79SzOEWtDgMHfw+7Tp4IedgXoqg M9sfyc5daCPkC6FFM16UUTREOoKaRJdiiLW1o7Ljaj7Rd+v3hgwC1vpyBmDwaPKJ +r7QmJ27IlmNANmOKsCeqNyq/YSBI8ON/t2ceOKzR23Y63KAfz0IXK1+Gvowp0lg /84Rw18YC8WLsTMmH0po7pDpmZIgmtfnfftjH6gz0n1stRcyFkuHarNO9SdRqS0/ 6wC1tDDWEpdufFgPVogfOxQggDqxydM0E+8PIaAqzrm2guGRYdpkQry0sEP5wQW+ 6LEZNSJS1VyK0i6JxuUUo9KCDC7uulj20+fCvYlYg9JP5r5qS2UzHYuG0wYCiDbz JAAzssbjG+8w0nW3JISy1g563Y1Y+kbr22SDG87Rm1e187iq8oChXhwZ1mCB4NUj nZW5EXMrZ3nQBvN32HWYCMb+Cw5DcthhasgJ2s92XRs7ghXxxtNn4kyFs9XeIZB3 ZVS7SSaFQOkqAY1NpVvuOz8UNjtBdy6pvrjty1lyP8/Ul63KaQxW7HBlGUqAcCON XBqJSQJhUHsGEBLlOlqJ4uRZ2+Vzzu8+lac1NUGAZmSp+9AgldYgvReETYC9Yn6J 5p4qoufjnbQ51K4S5SYc =pZKA -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org