public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-wireless/wireless-regdb/
Date: Sun,  1 Dec 2024 12:42:29 +0000 (UTC)	[thread overview]
Message-ID: <1733056798.af3eafe83f24eb3540d2110280a3df199c15c60d.sam@gentoo> (raw)

commit:     af3eafe83f24eb3540d2110280a3df199c15c60d
Author:     Stefan Linke <particleflux <AT> gmail <DOT> com>
AuthorDate: Mon Oct 21 19:20:44 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Dec  1 12:39:58 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=af3eafe8

net-wireless/wireless-regdb: fix typo in warning message

Signed-off-by: Stefan Linke <particleflux <AT> gmail.com>
Closes: https://github.com/gentoo/gentoo/pull/39071
Signed-off-by: Sam James <sam <AT> gentoo.org>

 net-wireless/wireless-regdb/wireless-regdb-20240508.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/net-wireless/wireless-regdb/wireless-regdb-20240508.ebuild b/net-wireless/wireless-regdb/wireless-regdb-20240508.ebuild
index 71d9858c1fc0..2b98135d4f43 100644
--- a/net-wireless/wireless-regdb/wireless-regdb-20240508.ebuild
+++ b/net-wireless/wireless-regdb/wireless-regdb-20240508.ebuild
@@ -27,7 +27,7 @@ pkg_pretend() {
 				ewarn "  or add regulatory.db and regulatory.db.p7s to CONFIG_EXTRA_FIRMWARE."
 			fi
 			if ! linux_chkconfig_present CFG80211; then
-				ewarn "REGULARTORY DOMAIN PROBLEM:"
+				ewarn "REGULATORY DOMAIN PROBLEM:"
 				ewarn "  With CONFIG_CFG80211 unset, the driver(s) won't be able to load the regulatory.db from"
 				ewarn "  /lib/firmware, resulting in broken regulatory domain support. Please set CONFIG_CFG80211=m."
 			fi


             reply	other threads:[~2024-12-01 12:42 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-01 12:42 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-01 11:51 [gentoo-commits] repo/gentoo:master commit in: net-wireless/wireless-regdb/ Sam James
2024-10-02 20:52 Sam James
2024-05-09  0:38 Rick Farina
2024-01-21  9:42 David Seifert
2023-08-23 20:27 Rick Farina
2023-08-19 20:58 Rick Farina
2023-08-19 16:52 Rick Farina
2023-08-19 16:52 Rick Farina
2023-08-19 16:52 Rick Farina
2023-08-19 16:52 Rick Farina
2023-06-17 15:13 Sam James
2023-03-19 23:10 Sam James
2022-06-06 16:56 Rick Farina
2022-06-06 16:56 Rick Farina
2022-05-05 23:48 WANG Xuerui
2022-04-08 16:48 Rick Farina
2022-04-04 14:56 Rick Farina
2022-04-04 14:56 Rick Farina
2021-10-04 20:40 Sam James
2021-05-18 15:52 Rick Farina
2021-05-18 15:52 Rick Farina
2021-05-18 15:52 Rick Farina
2021-02-27  3:56 Sam James
2021-02-26 15:56 Rick Farina
2021-02-12 10:33 Sam James
2021-02-03  9:56 Tony Vroon
2020-08-14 18:19 Rick Farina
2019-06-04  2:14 Rick Farina
2019-05-23  6:39 Aaron Bauman
2019-03-01 22:07 Rick Farina
2018-10-25  3:39 Richard Farina
2018-09-07 19:20 Richard Farina
2018-05-31 15:19 Richard Farina
2018-05-10 16:42 Richard Farina
2018-01-29  9:55 Tony Vroon
2018-01-26 18:05 Richard Farina
2017-03-08 22:46 Richard Farina
2016-06-10 15:46 Richard Farina
2016-05-02 22:18 Richard Farina
2016-02-08 22:47 Richard Farina
2015-10-22 17:00 Richard Farina
2015-09-30 17:30 Richard Farina

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=1733056798.af3eafe83f24eb3540d2110280a3df199c15c60d.sam@gentoo \
    --to=sam@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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