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

Reply via email to