From: Marlon Smith <marlon.smith10@gmail.com>
To: backports@vger.kernel.org
Subject: Backports not building configured drivers
Date: Mon, 27 Aug 2018 15:01:45 -0700 [thread overview]
Message-ID: <1535407305.25991.36.camel@gmail.com> (raw)
Hi everyone,
I'm using backports 4.14 to build for a custom kernel 3.14. That
kernel includes the RT2800 wifi driver, and if I configure backports
with menuconfig to build a newer version of that driver it works
perfectly. However, if I configure backports to build the RTL8821
driver, which my kernel otherwise does not include, the driver never
gets built and backports shows it as not selected the next time I run
menuconfig.
Is this expected behaviour? Is there something I can do to force this
driver to build?
Thanks!
Marlon
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next reply other threads:[~2018-08-28 1:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 22:01 Marlon Smith [this message]
2018-08-28 4:42 ` Backports not building configured drivers Luca Coelho
2018-08-29 20:55 ` Marlon Smith
2018-08-29 21:14 ` Larry Finger
2018-08-30 7:33 ` Johannes Berg
2018-08-30 16:07 ` Marlon Smith
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=1535407305.25991.36.camel@gmail.com \
--to=marlon.smith10@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).