From: Arunkumar K <Arunkumar.K@csr.com>
To: Arend van Spriel <arend@broadcom.com>,
"backports@vger.kernel.org" <backports@vger.kernel.org>
Subject: RE: Query regarding back porting of upstreamed Linux kernel drivers
Date: Tue, 14 Jul 2015 05:35:52 +0000 [thread overview]
Message-ID: <4fb66ea0da5940858c5f81362410ab68@BANASIEXM02.ASIA.ROOT.PRI> (raw)
In-Reply-To: <559FC80A.6090209@broadcom.com>
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
prev parent reply other threads:[~2015-07-14 5:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
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=4fb66ea0da5940858c5f81362410ab68@BANASIEXM02.ASIA.ROOT.PRI \
--to=arunkumar.k@csr.com \
--cc=arend@broadcom.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.