From: Leslie Rhorer <lesrhorer@att.net>
To: linux-kernel@vger.kernel.org, linux-modules@vger.kernel.org
Subject: Modules list
Date: Sun, 29 May 2022 06:35:19 -0500 [thread overview]
Message-ID: <dd7e69ce-41a4-cc5e-5a15-0ae9fc52aad0@att.net> (raw)
In-Reply-To: dd7e69ce-41a4-cc5e-5a15-0ae9fc52aad0.ref@att.net
I sent a subscription to the linux-modules list which seemed to be
successful, but when I sent a message, it bounced. I sent the message
to linux-modules@vger.kernel.org. Did I do something wrong?
next parent reply other threads:[~2022-05-29 11:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <dd7e69ce-41a4-cc5e-5a15-0ae9fc52aad0.ref@att.net>
2022-05-29 11:35 ` Leslie Rhorer [this message]
2022-05-29 15:21 ` Modules list Christophe Leroy
2022-05-29 15:41 ` Randy Dunlap
2022-05-29 23:45 ` Module failure on new install of Debian Bullseye Leslie Rhorer
2022-05-29 23:46 ` Leslie Rhorer
2022-05-30 6:08 ` Christophe Leroy
2022-05-30 6:43 ` Leslie Rhorer
2022-05-30 6:11 ` Christophe Leroy
2022-05-30 6:50 ` Leslie Rhorer
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=dd7e69ce-41a4-cc5e-5a15-0ae9fc52aad0@att.net \
--to=lesrhorer@att.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.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).