Linux Modules
 help / color / mirror / Atom feed
From: Leslie Rhorer <lesrhorer@att.net>
To: Luis Chamberlain <mcgrof@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	pmladek@suse.com
Cc: linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Majordomo not working
Date: Thu, 10 Aug 2023 22:48:17 -0500	[thread overview]
Message-ID: <06bc7efa-c486-f995-a73c-3f1dd6a5ce64@att.net> (raw)
In-Reply-To: <Y9BIU5SGOS6YEdSh@bombadil.infradead.org>

	I know this is not exactly the right place to post this, but I am at a 
complete loss what else to do.  Please forgive me, but I cannot get the 
Majordomo at vger.kernel.org to respond to me.  I have tried everything 
of which I can think, but the Majordomo will not recognize when I send 
it the authorization command in order to try and include my 
siliconventures.net address in the linux-modules mailing list.  My 
att.net address is supposed to already be a member of the list, but 
whenever I send to the linux-modules list from mt AT&T address, the 
message bounces.

	Thus , I seem to be having two issues.  The more immediate is I cannot 
get any messages through to where they need to go, both to the Majordomo 
and to the linux-modules list.  The more important long term issue is I 
am having a problem with the NIC card on one of my Debian Linux servers.

  parent reply	other threads:[~2023-08-11  3:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24 21:06 [GIT PULL] modules changes for v6.2-rc6 Luis Chamberlain
2023-01-25  2:23 ` pr-tracker-bot
2023-08-11  3:48 ` Leslie Rhorer [this message]
2023-08-11  3:53   ` Majordomo not working Leslie Rhorer
2023-08-11  4:46     ` Randy Dunlap
2023-08-11 16:51       ` Leslie Rhorer
2023-08-11 16:55         ` Randy Dunlap
2023-08-13 18:32           ` 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=06bc7efa-c486-f995-a73c-3f1dd6a5ce64@att.net \
    --to=lesrhorer@att.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=pmladek@suse.com \
    --cc=torvalds@linux-foundation.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