From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: rpi-base: don't install snd_bcm2835.conf module file, move udev rules to separate file
Date: Wed, 30 Sep 2020 22:17:23 +0200 [thread overview]
Message-ID: <20200930201723.MEtu060JjYhn_4eJnjNEw4aNjMQNM0xjIIydgmiBvSg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24844@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 205 bytes --]
New comment by Johnnynator on void-packages repository
https://github.com/void-linux/void-packages/pull/24844#issuecomment-701621441
Comment:
Please also increase the revision in `rpi-firmware/template`
next prev parent reply other threads:[~2020-09-30 20:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 4:38 [PR PATCH] [RFC] rpi-base: don't install snd_bcm2835.conf module file, move udev rules to separate file, add gpio udev rules amak79
2020-09-13 0:46 ` [PR PATCH] [Updated] " amak79
2020-09-13 2:25 ` amak79
2020-09-29 2:30 ` rpi-base: don't install snd_bcm2835.conf module file, move udev rules to separate file ericonr
2020-09-30 0:05 ` fosslinux
2020-09-30 0:05 ` fosslinux
2020-09-30 0:47 ` pbui
2020-09-30 1:23 ` amak79
2020-09-30 1:56 ` [PR PATCH] [Updated] " amak79
2020-09-30 2:05 ` amak79
2020-09-30 2:35 ` amak79
2020-09-30 2:36 ` amak79
2020-09-30 10:33 ` fosslinux
2020-09-30 20:17 ` Johnnynator [this message]
2020-09-30 22:42 ` [PR PATCH] [Updated] " amak79
2020-09-30 23:03 ` amak79
2020-10-01 0:06 ` amak79
2020-10-21 23:33 ` [PR PATCH] [Updated] " amak79
2020-11-10 3:50 ` amak79
2020-11-10 6:43 ` amak79
2020-11-10 6:47 ` amak79
2020-11-12 0:39 ` amak79
2020-12-30 7:12 ` the-maldridge
2020-12-30 7:41 ` [PR PATCH] [Updated] " amak79
2020-12-30 8:16 ` amak79
2020-12-30 8:24 ` [PR PATCH] [Merged]: " the-maldridge
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=20200930201723.MEtu060JjYhn_4eJnjNEw4aNjMQNM0xjIIydgmiBvSg@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).