Update to v7 from kernel.org #59
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I reported those problems upstream. The main developer knows about them, but did not wish to change his v7 version as it was reviewed. The patches will be sent to wireless-drivers-next once it actually appears there. The driver was accepted today. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I update the v6 branch to v7 using the code currently committed to kernel.org:kvalo/wireless-drivers-next.
There are also a lot of backport related fixes that are (as expected) not included upstream, but I did my best to preserve them in 9648c7f.
@lwfinger Is there a reason why the null pointer check of
sec_cam->sec_cam_idxand intialization ofbufin_set_bt_tx_poweris not included upstream?