Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753401AbbFAUDa (ORCPT ); Mon, 1 Jun 2015 16:03:30 -0400 Received: from mail3-relais-sop.national.inria.fr ([192.134.164.104]:23788 "EHLO mail3-relais-sop.national.inria.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751588AbbFAUDX (ORCPT ); Mon, 1 Jun 2015 16:03:23 -0400 X-IronPort-AV: E=Sophos;i="5.13,534,1427752800"; d="scan'208";a="132936668" Date: Mon, 1 Jun 2015 22:03:20 +0200 (CEST) From: Julia Lawall X-X-Sender: jll@localhost6.localdomain6 To: Felix Fietkau cc: "Luis R. Rodriguez" , "backports@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: Uses of Linux backports in the industry In-Reply-To: <556CA991.7030302@openwrt.org> Message-ID: References: <556CA991.7030302@openwrt.org> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1866 Lines: 37 On Mon, 1 Jun 2015, Felix Fietkau wrote: > On 2015-05-29 04:54, Luis R. Rodriguez wrote: > > Me and Julia are working on a paper which evaluates use of Coccinelle > > on backports, a preliminary draft of such paper can be found on github > > [0]. We are making some tweaks to this, one of which is covering the > > uses of Linux backports [1] in the industry, for this we'd like to try > > to get feedback as to where and how folks are using backports. Please > > let me and Julia know -- or if the information is not sensitive please > > feel free to just reply to this thread and share with others. All > > feedback is greatly appreciated. If you are OK in having us list or > > generalize your usage please indicate so. > In OpenWrt, we use backports to stay up to date with current wireless > drivers without being forced into frequently updating the kernels as > well. We support many different platforms, and sometimes it takes a > while to update the kernel on them. > Using backports significantly reduces the amount of effort that we need > to put into maintaining the wireless drivers. > When making changes to wireless drivers or mac80211, which I submit > upstream, I also develop them in our most recent backports snapshot > first (typically generated from wireless-testing). When they are done, I > port them to a proper git tree and submit them from there. > > In OpenWrt, we typically update the backports snapshot outside of the > normal kernel release cycle (always to latest wireless-testing) and > stabilize that by cherry-picking individual patches on top of it. Thanks for the feedback! julia -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/