From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: AceLan Kao <acelan.kao@canonical.com>
Cc: Johannes Berg <johannes.berg@intel.com>,
hauke@hauke-m.de, mcgrof@kernel.org, backports@vger.kernel.org,
Anthony Wong <anthony.wong@canonical.com>
Subject: Re: Adding the BT driver
Date: Thu, 13 Jul 2017 11:21:36 +0200 [thread overview]
Message-ID: <59673BA0.20703@broadcom.com> (raw)
In-Reply-To: <CAFv23QnvFGj3b2GCV=v=mGk8JgGwZRe+W-+m9gxbtAsChySz=Q@mail.gmail.com>
On 7/13/2017 5:07 AM, AceLan Kao wrote:
> Hi all,
>
> I'm working on adding BT driver back to linux backport driver, and got
> some questions.
I suppose it means you also want to maintain BT support in backports
project?
> 1. Do we still do building the backport driver against all the
> supported kernels? I didn't see those reports in git log recently, so
> I'm wondering while backporting BT driver, can I skip some old
> kernels' support.
Well. You could limit the earliest kernel by adding a dependency in the
dependencies file.
> 2. Is there a script that can help me to build the backport driver
> against certain kernels?
Not really. You just run make from the backports package and provide
KLIB_BUILD=... on the command line referring to the target kernel headers.
> 3. Is there anything I should take care of while doing the BT backport?
I forgot the reason for dropping BT. Don't think it was anything
technical. I guess there was nobody willing to put effort in it.
Regards,
Arend
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2017-07-13 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 3:07 Adding the BT driver AceLan Kao
2017-07-13 9:21 ` Arend van Spriel [this message]
2017-07-13 17:28 ` Luis R. Rodriguez
2017-07-14 2:38 ` AceLan Kao
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=59673BA0.20703@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=acelan.kao@canonical.com \
--cc=anthony.wong@canonical.com \
--cc=backports@vger.kernel.org \
--cc=hauke@hauke-m.de \
--cc=johannes.berg@intel.com \
--cc=mcgrof@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.