From: CameronNemo <CameronNemo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pinebookpro: kernel: update to 6.1.9, base: drop firmware dependency, use ALSA UCM
Date: Fri, 17 Feb 2023 06:30:59 +0100 [thread overview]
Message-ID: <20230217053059.EQ4crWiax2x7s6UflmNRFtj7GOm80A1mFbTBV5eDDDU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41062@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1928 bytes --]
New comment by CameronNemo on void-packages repository
https://github.com/void-linux/void-packages/pull/41062#issuecomment-1434123591
Comment:
>From what I can tell, Manjaro is currently, and has been, actively upstreaming their own patches
Yeah, no. They upstream some, sometimes. Mostly they pull in patches that will never be accepted upstream, like the altmode DP patches.
>Is your position that the pinebookpro-kernel template should never include any patches beyond those made to our linuxX.Y templates? If so, why are we using the pinebookpro-kernel template, in the first place?
Yeah I think we should be removing patches and eventually get rid of the device specific kernel. Debian, for example, supports the PBP but uses their generic ARM64 kernel to do so. PostmarketOS has a [linux-postmarketos-rockchip package](https://gitlab.com/postmarketOS/pmaports/-/blob/master/device/community/linux-postmarketos-rockchip/APKBUILD) that is a completely unpatched kernel, which they use for the PBP and some other Rockchip devices.
>why are 5 out of 6 patches in the pinebookpro-kernel template now seemingly from a nearly 2-year old version of Manjaro?
They cannot be upstreamed or were never submitted, but fix issues that I could personally reproduce.
>one of the latest pbp-specific Manjaro-origin patches
By "latest", I hope you realize that is a patch that was written 9 months ago and never sent upstream. Send it upstream! If they accept it, you can pull it in without me objecting. I have personally never run into any issues with the microSD card slot, and I have used a variety of microSD cards. Maybe I am lucky? Are you actually seeing errors with the microSD card slot? I've not heard anyone complain who uses Void.
I think this conversation is going in circles so I am going to unsubscribe. Feel free to CC me on any future patches you send upstream or PRs you submit to Void, though.
next prev parent reply other threads:[~2023-02-17 5:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 16:12 [PR PATCH] pinebookpro-kernel: update to 6.1.0 CameronNemo
2022-12-21 18:58 ` [PR PATCH] [Updated] pinebookpro-kernel: update to 6.1.1 CameronNemo
2023-02-06 2:29 ` CameronNemo
2023-02-06 2:32 ` pinebookpro: kernel: update to 6.1.1, base: drop firmware dependency, use ALSA UCM CameronNemo
2023-02-06 12:18 ` petersen77
2023-02-06 15:46 ` CameronNemo
2023-02-06 15:48 ` CameronNemo
2023-02-08 21:54 ` pinebookpro: kernel: update to 6.1.9, " petersen77
2023-02-14 20:59 ` [PR PATCH] [Merged]: " paper42
2023-02-14 23:04 ` atweiden
2023-02-15 1:11 ` CameronNemo
2023-02-15 3:18 ` atweiden
2023-02-15 16:29 ` CameronNemo
2023-02-15 16:29 ` CameronNemo
2023-02-16 3:57 ` atweiden
2023-02-16 5:26 ` CameronNemo
2023-02-16 6:56 ` atweiden
2023-02-16 9:14 ` CameronNemo
2023-02-17 4:25 ` atweiden
2023-02-17 5:30 ` CameronNemo
2023-02-17 5:30 ` CameronNemo [this message]
2023-02-17 19:45 ` atweiden
2023-02-17 22:53 ` CameronNemo
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=20230217053059.EQ4crWiax2x7s6UflmNRFtj7GOm80A1mFbTBV5eDDDU@z \
--to=cameronnemo@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).