-
Notifications
You must be signed in to change notification settings - Fork 50
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
Rebase to 6.4-rc2+ #136
Comments
@kwizart clamor-s/linux@5b91414 or you can use my grate-base branch for now. I am waiting for 6.4 stable. |
@clamor-s Thanks, it worksforme, (tested on PAZ00) but for some reason the emc-table patch was dropped, I should be able to rebase if something broke with it... |
@kwizart my grate-base contains just bare minimum for testing devices I own. I could miss some changes, if you need those, just pick from main grate/linux repo. |
Kernel is rebased now on recent linux-next |
There is no history for the drm/grate, it always was a single commit |
@digetx I was thinking of tearing the grate/linux apart and creating a set of device dedicated branches + base branch and then just squash them all from time to time once there are major updates. In this case you can focus on base generic stuff while other branches like |
Good to me |
@digetx @kwizart this is partially done re-factoring, a concept of what I mean. https://github.com/clamor-s/linux-concept
|
I'm fine having more than the strict necessary for my devices. (I'm using paz00/trimslice/jetson-tk1 , have tf701/nyan-big near). So I only plan to build a single kernel for all of them. But having them in branches make senses if different maintainers can update independently ... Transformer branch is still a "collective" works with less devices, so It only changes the "scale", not the need to coordinate. Also this conversation within this ticket make senses to me since I exactly had to forward patches to various maintainers in order to rebase to newer kernel. and hopefully the maintainer didn't had a diverging copy of the patches in WIP (because they would have updated it on their side). So I'm not sure if splitting into devices branches solves all problems, but at least it will probably helps to share the work when rebasing branches... |
There still should be a master branch with, for example, rebase of all branches on stable releases.
I am the one who maintains all transformers and most patches related to them go through my repos.
There is no universal solution unfortunately |
Let's close this as the current rebase exists. |
I've rebased grate/linux on top of 6.4-rc2 and this needs the following fixes that needs squashing (at least).
The text was updated successfully, but these errors were encountered: