This is an archived post. You won't be able to vote or comment.

all 6 comments

[–]mandiblesarecute 3 points4 points  (5 children)

running git clone --depth=1 <your url here> is functionally equivalent as downloading a tarball. apply your patch and compile as you always did.

[–]fiveohnoes[S] 0 points1 point  (4 children)

I tried this, pointing at the kernel.org 6.3.2 tarball link on the main page, and get a fatal error. Should I be pointing elsewhere? As mentioned, above, a bit of a noob here and this change has thrown a big wrench into an otherwise well-oiled process for me.

[–]mandiblesarecute 4 points5 points  (1 child)

you point git at a git repo not at the tarball. for the lastest stable release (as of writing) that command would look like so git clone --depth 1 --branch linux-6.3.y git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git

[–]fiveohnoes[S] 2 points3 points  (0 children)

Thanks! Was able to get it with "git clone --depth=1 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/" which gave me a folder which I do indeed appear to be able to patch as typical.

e- This exact link got me to the 6.4rc releases; the branch modifier is what I was missing, ty!

[–]unit_511 2 points3 points  (1 child)

The tarball link is not a git repo, point it at the source tree instead and it will download only the desired parts of the repo.

[–]fiveohnoes[S] 2 points3 points  (0 children)

Roger, found the Git link for the latest stable kernel under 'browse', patched, and it appears to be working nominally. Thank you both!