From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: "<debian-sparc@lists.debian.org>" <debian-sparc@lists.debian.org>
Cc: gentoo-sparc <gentoo-sparc@lists.gentoo.org>,
sparclinux <sparclinux@vger.kernel.org>
Subject: Finding SPARC patches worth upstreaming in the UEK kernel
Date: Sat, 25 Oct 2025 10:56:40 +0200 [thread overview]
Message-ID: <cf8d79b35a3df1dd79fe3475b0e78ac50754b456.camel@physik.fu-berlin.de> (raw)
Hi,
as many of you may know, Oracle's UEK kernel for SPARC contains a number of improvements
that never made it upstream into the Linux kernel. Since it would be a waste to not pick
those up, I have started creating issues in the sparclinux issue tracker on GitHub [1]
to collect these. Since I can't do this all on my own, I invite everyone interested to
help with this effort.
To do so, just take a look at the commit history of the arch/sparc directory of the
UEK kernel [2] and scroll through the commits. If you spot a commit that might be
worth upstreaming such as [3] ("sparc64: Add missing hardware capabilities for M7"),
create a new issue like I have done for this commit in [4].
Some notes:
- Please include links with the commit title to the commits in the UEK sources; this
can be achieved by selecting the text of the commit message in the commit overview
in [2], then right-click and copy. This will automatically copy a URL with the commit
title into the clipboard using the correct "[]()" template.
- Before opening an issue, please make sure that the issue doesn't exist yet.
- Use GitHub labels such as "patch", "kernel", "bug" and "enhancement" to tag the issue
similar to the existing issue.
There might also be interesting commits in the drivers directory [5], so please look there
as well. Oracle stopped working on SPARC support for Linux around 2017, so you will most
likely find the interesting commits starting at the end of 2017 going backwards.
Adrian
> [1] https://github.com/sparclinux/issues/issues
> [2] https://github.com/sparclinux/linux-uek/commits/uek4/qu7/arch/sparc
> [3] https://github.com/sparclinux/linux-uek/commit/efcafbab1b123d615c1f2683c98fccc5ccee1527
> [4] https://github.com/sparclinux/issues/issues/17
> [5] https://github.com/sparclinux/linux-uek/commits/uek4/qu7/drivers
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
reply other threads:[~2025-10-25 8:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cf8d79b35a3df1dd79fe3475b0e78ac50754b456.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=debian-sparc@lists.debian.org \
--cc=gentoo-sparc@lists.gentoo.org \
--cc=sparclinux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).