From: David Hildenbrand <david@redhat.com>
To: linux-kernel@vger.kernel.org, Matthew Wilcox <willy@infradead.org>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
Oscar Salvador <osalvador@suse.de>, Zi Yan <ziy@nvidia.com>
Subject: linux-mm mailing list problems
Date: Thu, 5 Dec 2024 13:12:50 +0100 [thread overview]
Message-ID: <dc19ac6a-51ae-406a-85e9-c4acf2ecb80a@redhat.com> (raw)
In-Reply-To: <20241205085217.2086353-1-david@redhat.com>
On 05.12.24 09:52, David Hildenbrand wrote:
> Sending this via the RH SMTP first, because IT doesn't see any obvious
> problems why the mails shouldn't be reaching linux-mm, so let's see if
> the problems are gone now. If this doesn't work, I'll resend them
> using the known-working gmail SMTP. Sorry already for the noise ...
I talked to RH IT, and it looks like the mails get delivered to
linux-mm@kvack.org just fine, and linux-mm decides to silently drop them.
Does anybody know who maintains linux-mm@kvack.org? I wrote a mail to
mbot@kvack.org, but I am pretty sure that is the wrong address.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-12-05 12:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 8:52 [PATCH v1 0/2] mm: don't use __GFP_HARDWALL when migrating remote pages David Hildenbrand
2024-12-05 8:52 ` [PATCH v1 1/2] mm/page_alloc: don't use __GFP_HARDWALL when migrating pages via alloc_contig*() David Hildenbrand
2024-12-09 7:47 ` Oscar Salvador
2024-12-05 8:52 ` [PATCH v1 2/2] mm/memory_hotplug: don't use __GFP_HARDWALL when migrating pages via memory offlining David Hildenbrand
2024-12-09 7:48 ` Oscar Salvador
2024-12-05 12:12 ` David Hildenbrand [this message]
2024-12-05 14:43 ` linux-mm mailing list problems Vlastimil Babka
2024-12-05 15:42 ` Benjamin LaHaise
2024-12-05 15:52 ` David Hildenbrand
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=dc19ac6a-51ae-406a-85e9-c4acf2ecb80a@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=ziy@nvidia.com \
/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