Return-path: Received: from mail-la0-f45.google.com ([209.85.215.45]:41332 "EHLO mail-la0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753848AbaKRSV3 (ORCPT ); Tue, 18 Nov 2014 13:21:29 -0500 MIME-Version: 1.0 From: "Luis R. Rodriguez" Date: Tue, 18 Nov 2014 10:21:05 -0800 Message-ID: (sfid-20141118_192157_810821_3BF544A2) Subject: [ANN] Kernel integration now merged on backports To: "backports@vger.kernel.org" Cc: "linux-kernel@vger.kernel.org" , linux-wireless , linux-media@vger.kernel.org, linux-bluetooth , "netdev@vger.kernel.org" , linux-wpan@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: Full kernel integration is now merged as part of Linux backports-20141114. I've written a bit about it [0] [1], what we need now are users and developer to give this a good spin as we wind down for the v3.19 release, which will be the first release that will support kernel integration down to any kernel >= 3.0 -- for now you can use the backports-20141114 tag which uses as base supported drivers from next-20141114. What this will mean is that you can opt in to integrate any device driver we support from any future backports release into any of >= 3.0 kernel with full kconfig support, enabling you to build everything as built-in. For all this you won't be using the packaged releases [2], instead you'll use the git tree directly as documented. [0] http://www.do-not-panic.com/2014/11/automating-backport-kernel-integration.html [1] https://backports.wiki.kernel.org/index.php/Documentation/integration [2] https://backports.wiki.kernel.org/index.php/Documentation/packaging Luis