All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
* Query regarding back porting of upstreamed Linux kernel drivers
@ 2015-07-10 11:22 Arunkumar K
  2015-07-10 13:26 ` Arend van Spriel
  0 siblings, 1 reply; 3+ messages in thread
From: Arunkumar K @ 2015-07-10 11:22 UTC (permalink / raw)
  To: backports@vger.kernel.org

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Query regarding back porting of upstreamed Linux kernel drivers
  2015-07-10 11:22 Query regarding back porting of upstreamed Linux kernel drivers Arunkumar K
@ 2015-07-10 13:26 ` Arend van Spriel
  2015-07-14  5:35   ` Arunkumar K
  0 siblings, 1 reply; 3+ messages in thread
From: Arend van Spriel @ 2015-07-10 13:26 UTC (permalink / raw)
  To: Arunkumar K, backports@vger.kernel.org

On 07/10/2015 01:22 PM, Arunkumar K wrote:
> 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?

Guess the one with most incentive will do it.

>
>  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?

That is a problem that backports can not solve. So you could manually 
backport your new driver into the backport-3.14 tarball to minimize your 
effort.

Regards,
Arend

> 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
>

--
To unsubscribe from this list: send the line "unsubscribe backports" in

^ permalink raw reply	[flat|nested] 3+ messages in thread

* RE: Query regarding back porting of upstreamed Linux kernel drivers
  2015-07-10 13:26 ` Arend van Spriel
@ 2015-07-14  5:35   ` Arunkumar K
  0 siblings, 0 replies; 3+ messages in thread
From: Arunkumar K @ 2015-07-14  5:35 UTC (permalink / raw)
  To: Arend van Spriel, backports@vger.kernel.org

Thanks for your response Arend.

Regards,
Arun

-----Original Message-----
From: Arend van Spriel [mailto:arend@broadcom.com] 
Sent: 10 July 2015 18:57
To: Arunkumar K; backports@vger.kernel.org
Subject: Re: Query regarding back porting of upstreamed Linux kernel drivers

On 07/10/2015 01:22 PM, Arunkumar K wrote:
> 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?

Guess the one with most incentive will do it.

>
>  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?

That is a problem that backports can not solve. So you could manually backport your new driver into the backport-3.14 tarball to minimize your effort.

Regards,
Arend

> 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
>



 To report this email as spam click https://www.mailcontrol.com/sr/71ZG6X1WMXbGX2PQPOmvUqW!RI4xIDLrpnWLJ2TOncz1J54P8Pz2BYKVEZWF1MWbmXpsabQE6AvgE3KctAewCA== .
--
To unsubscribe from this list: send the line "unsubscribe backports" in

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-07-14  5:36 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-07-10 11:22 Query regarding back porting of upstreamed Linux kernel drivers Arunkumar K
2015-07-10 13:26 ` Arend van Spriel
2015-07-14  5:35   ` Arunkumar K

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.