Linux backports project
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: "backports@vger.kernel.org" <backports@vger.kernel.org>,
	Julia Lawall <julia.lawall@lip6.fr>
Subject: Re: Uses of Linux backports in the industry
Date: Fri, 29 May 2015 10:08:22 +0200	[thread overview]
Message-ID: <55681E76.4070401@broadcom.com> (raw)
In-Reply-To: <1432882836.2104.1.camel@sipsolutions.net>

On 05/29/15 09:00, Johannes Berg wrote:
> -lkml, that list is overfull anyway ...
>
> On Thu, 2015-05-28 at 19:54 -0700, 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.

We use the backports project solely for testing. We build and test 
nightly for a number of lab machines. Some are running recent 
wireless-testing kernel, but a number of those run a relatively old FC19 
kernel (3.11.1) for which we build backport brcm80211 drivers. We do 
that for our internal tree and for the wireless-testing tree.

>> If you are OK in having us list or
>> generalize your usage please indicate so.

Go ahead and make your list ;-)

Regards,
Arend

> We've just published one of our internal git trees that is actually
> based on backports:
> https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/backport-iwlwifi.git/
>
> johannes
>
> --
> To unsubscribe from this list: send the line "unsubscribe backports" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2015-05-29  8:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-29  2:54 Uses of Linux backports in the industry Luis R. Rodriguez
2015-05-29  7:00 ` Johannes Berg
2015-05-29  8:08   ` Arend van Spriel [this message]
2015-05-29  8:29     ` Julia Lawall
2015-05-29 16:41     ` Arend van Spriel
2015-05-29 16:33   ` Luis R. Rodriguez
2015-05-29 18:47     ` Johannes Berg
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
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=55681E76.4070401@broadcom.com \
    --to=arend@broadcom.com \
    --cc=backports@vger.kernel.org \
    --cc=julia.lawall@lip6.fr \
    --cc=mcgrof@do-not-panic.com \
    /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