From: Arunkumar K <Arunkumar.K@csr.com>
To: "backports@vger.kernel.org" <backports@vger.kernel.org>
Subject: Query regarding back porting of upstreamed Linux kernel drivers
Date: Fri, 10 Jul 2015 11:22:52 +0000 [thread overview]
Message-ID: <b43797e602f34e10a7924f0d3b6a1368@BANASIEXM02.ASIA.ROOT.PRI> (raw)
Hi,
I have the following queries regarding back porting of up-streamed Linux kernel driver:
Suppose a new driver is added to Linux mainline in release 4.2, will the developer who added new driver to the mainline need to submit the changes for back porting to the backports git?
Or will the backports project team be doing the back porting of the new driver?
>From the following page https://backports.wiki.kernel.org/index.php/Main_Page
"Current versions of backports support all mainline kernels starting with version 3.0, for kernel versions older than 3.0 please use backports-3.14, which supports all kernel versions back to 2.6.26."
Suppose we have release backports-4.2 and new driver has been backported. Will it have support only till kernel version 3.0. Suppose if the new driver needs to be supported in version 2.6.32 what is the process followed?
Regards,
Arun
Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom
More information can be found at www.csr.com. Keep up to date with CSR on our technical blog, www.csr.com/blog, CSR people blog, www.csr.com/people, YouTube, www.youtube.com/user/CSRplc, Facebook, www.facebook.com/pages/CSR/191038434253534, or follow us on Twitter at www.twitter.com/CSR_plc.
You can now access the wide range of products powered by aptX at www.aptx.com
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next reply other threads:[~2015-07-10 11:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 11:22 Arunkumar K [this message]
2015-07-10 13:26 ` Query regarding back porting of upstreamed Linux kernel drivers Arend van Spriel
2015-07-14 5:35 ` Arunkumar K
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=b43797e602f34e10a7924f0d3b6a1368@BANASIEXM02.ASIA.ROOT.PRI \
--to=arunkumar.k@csr.com \
--cc=backports@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.