You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The easiest way to do this is to use an online kernel source browser like this one. This allows you to easily switch between different kernel versions and lookup symbols appearing in the stacktrace. Although it does not index kernel code used by GCP or AWS it is still very handy.
Highlight is my own.
This is not really our field but it should be rather straight forward:
Find the Git remotes.
Rename the Git tags from those remotes inside script.sh.
Only question: how should the tags be structured? Add entries inside the existing minor menus? Add new minor menus for those kernels? Add new major menus?
Nothing urgent.
The text was updated successfully, but these errors were encountered:
Maybe having a separate entry for linux-gcp, linux-aws and linux-android would make sense?
But then it probably would be cool to actually allow users to view diffs between upstream and vendor versions when that gets finished...
The annoying thing about the versions menu is that it's very big, to the point where its impact is noticeable during site load (dir/source view does not flash on musl like it does on linux). I'm wondering if it wouldn't make sense to move it to js. Then having twice the tags we have right now, but for aws/gcp/azure/android... wouldn't be a problem
Reading this article:
Highlight is my own.
This is not really our field but it should be rather straight forward:
script.sh
.Only question: how should the tags be structured? Add entries inside the existing minor menus? Add new minor menus for those kernels? Add new major menus?
Nothing urgent.
The text was updated successfully, but these errors were encountered: