-
Notifications
You must be signed in to change notification settings - Fork 2
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
Misc cleanup. Remove support for FreeBSD < 12 #3
base: reno
Are you sure you want to change the base?
Conversation
Generally, each change there, which is not a sincere bugfix, means the work for me when new vendor code drop is released. Unless you can convince Realtek to import our changes into their codebase, I am in fact leery to apply such cleanups. At least we should try to keep bugfixes and cleanups separated. I did not thought how to organize the workflow to make it feasible. Might be there should be a branch on top of the 'my' branch, where 'my' only contains bug fixes, rebased. |
@kostikbel ok let's do a second branch where we make these cleanups. I will split the cleanups out as you asked above. I am talking with RealTek now, they seem willing to work with us. |
@kostikbel my desire is to merge this into src/main as re(9) since the in tree one is problematic. We will definitely want to coordinate with RealTek in any case. I have a punch-list of things I'd like to do from reading the code many times. Maybe you can add to this anything else that would be necessary to get it into main?
I do not think these are necessary for main but would be nice stretch goals:
|
What you have in those 4 commits looks fine to me. I am unsure what to do next there. Do you want to keep the cleanup work on your fork/branch? Or do you prefer for me to accept the pull requests for it? I created the 'reno' branch in my repo if you want PRs. Please create requests against this branch. |
@kostikbel I'd like to work on this driver with you and get it into the tree. This is my first pass at removing some unneeded code.