From: Julia Lawall <julia.lawall@lip6.fr>
To: Felix Fietkau <nbd@openwrt.org>
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
"backports@vger.kernel.org" <backports@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Uses of Linux backports in the industry
Date: Mon, 1 Jun 2015 22:03:20 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1506012203070.2222@localhost6.localdomain6> (raw)
In-Reply-To: <556CA991.7030302@openwrt.org>
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
next prev parent reply other threads:[~2015-06-01 20:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 2:54 Luis R. Rodriguez
2015-05-29 14:53 ` Enrico Weigelt, metux IT consult
2015-05-29 15:01 ` Richard Weinberger
2015-05-29 17:36 ` Theodore Ts'o
2015-05-29 17:51 ` Luis R. Rodriguez
2015-06-23 18:49 ` Pavel Machek
2015-06-24 9:12 ` Enrico Weigelt, metux IT consult
2015-06-24 9:09 ` Enrico Weigelt, metux IT consult
2015-06-24 9:19 ` Richard Weinberger
2015-06-24 9:55 ` Enrico Weigelt, metux IT consult
2015-06-24 10:18 ` Richard Weinberger
2015-06-01 18:50 ` Felix Fietkau
2015-06-01 20:03 ` Julia Lawall [this message]
2015-06-24 10:13 ` Enrico Weigelt, metux IT consult
2015-06-02 19:05 ` Szymon Janc
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1506012203070.2222@localhost6.localdomain6 \
--to=julia.lawall@lip6.fr \
--cc=backports@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=nbd@openwrt.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®