From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pinebookpro-kernel: update to 5.15.16
Date: Tue, 25 Jan 2022 11:37:45 +0100 [thread overview]
Message-ID: <20220125103745.bJIdmbfEQTmCSeA-zrvofYqHuCY30QEVHgJIVx2_CJs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35216@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 294 bytes --]
New comment by Johnnynator on void-packages repository
https://github.com/void-linux/void-packages/pull/35216#issuecomment-1021045280
Comment:
This still seems to be affected by the problem that fusb302 is not picked up by dracut.
Probably just set `CONFIG_TYPEC_FUSB302=y` in the dotconfig
next prev parent reply other threads:[~2022-01-25 10:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 2:11 [PR PATCH] " CameronNemo
2022-01-25 10:37 ` Johnnynator [this message]
2022-01-25 18:14 ` Johnnynator
2022-01-25 20:17 ` CameronNemo
2022-01-25 20:18 ` CameronNemo
2022-01-25 22:13 ` Johnnynator
2022-01-30 12:30 ` Johnnynator
2022-03-11 18:32 ` [PR PATCH] [Updated] " CameronNemo
2022-03-11 18:34 ` CameronNemo
2022-03-11 18:34 ` CameronNemo
2022-03-12 7:05 ` [PR PATCH] [Updated] pinebookpro-kernel: update to 5.15.27 CameronNemo
2022-03-12 7:05 ` CameronNemo
2022-04-09 22:39 ` [PR PATCH] [Updated] pinebookpro-kernel: update to 5.15.28 CameronNemo
2022-04-10 1:20 ` CameronNemo
2022-04-10 3:23 ` pinebookpro-kernel: update to 5.15.33 CameronNemo
2022-04-13 23:32 ` [PR PATCH] [Updated] " CameronNemo
2022-04-13 23:44 ` pinebookpro-kernel: update to 5.15.34 CameronNemo
2022-04-13 23:44 ` CameronNemo
2022-05-09 19:36 ` [PR PATCH] [Updated] " CameronNemo
2022-05-09 21:40 ` [PR PATCH] [Merged]: pinebookpro-kernel: update to 5.15.38 paper42
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=20220125103745.bJIdmbfEQTmCSeA-zrvofYqHuCY30QEVHgJIVx2_CJs@z \
--to=johnnynator@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).