Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix building against 4.12 #158

Merged
merged 1 commit into from
Jul 16, 2017
Merged

Conversation

karolherbst
Copy link
Contributor

it still works for 4.11, didn't test older kernels

@Lekensteyn
Copy link
Member

Should work with older kernels too, it was first introduced with torvalds/linux@c22ce14 which includes asm/uaccess.h

Thanks!

@Lekensteyn Lekensteyn merged commit 9dd2270 into Bumblebee-Project:master Jul 16, 2017
@Lekensteyn
Copy link
Member

Oops, accidentally merged to master. Now force-pushed (sorry!) the previous master and fast-forwarded the change to develop branch

@karolherbst
Copy link
Contributor Author

@Lekensteyn ohh right, I should have made the request against develop. Maybe it makes sense to move the default branch to develop as well, as this affects the default branches for cloning/PRs as well?

@karolherbst karolherbst deleted the fix_4.12 branch July 17, 2017 13:15
@Lekensteyn
Copy link
Member

Normally the master branch is the stable version that should be used, but as there is not that much development now it might indeed make sense to mark the develop branch as default. I'll think about it.

@metabubble
Copy link

When will that change reflect in the bumblebee gentoo overlay?

@karolherbst
Copy link
Contributor Author

@metabubble you can change the branch of the live ebuild, you could add this to your portage settings: "bbswitch_LIVE_BRANCH=develop"

@Nnami32 Nnami32 linked an issue Jun 23, 2023 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Network Analyzer: Ping '172.0.0.34'
3 participants