From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: palmerdabbelt@google.com, linux-kernel@vger.kernel.org,
Atish Patra <atish.patra@wdc.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
guoren@kernel.org, linux-riscv@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/4] initrd: Use unified initrd reserve function in ARM/RISCV
Date: Mon, 18 Jan 2021 09:17:33 +0000 [thread overview]
Message-ID: <20210118091733.GD1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <cc47f8cf-8778-43ab-77de-9dd220de7c26@huawei.com>
On Mon, Jan 18, 2021 at 09:01:40AM +0800, Kefeng Wang wrote:
>
> On 2021/1/17 18:09, Russell King - ARM Linux admin wrote:
> > On Sun, Jan 17, 2021 at 12:57:55PM +0800, Kefeng Wang wrote:
> > > Correct Russell's mail address (from linux@armlinux.org.uk to
> > > rmk+kernel@armlinux.org.uk, should update the MAINTAINERS)
> > No. MAINTAINERS is correct.
>
> I got following message, so I check mail of your recent patches, and send a
> new one.
>
> Please ignore it, there may be some other problems.
>
> "*Delivery has failed to these recipients or groups:*
>
> linux@armlinux.org.uk <mailto:linux@armlinux.org.uk>
> A communication failure occurred during the delivery of this message. Please
> to resend the message later. If the problem continues, contact your
> helpdesk."
That is a most unhelpful bounce message - I suppose it's designed for
non-technical people to ensure that the problem can't be resolved.
From what I can see from my end, every attempt involving your email
address last week (wangkefeng.wang@huawei.com) has been successful, so
I suspect the problem is not at my end.
In any case, all @armlinux.org.uk addresses hit the same server, so
if there's a "communication failure" for the domain, it would affect
all local-parts equally.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-01-18 9:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 5:46 [PATCH v3 0/4] initrd: Use unified initrd reserve function in ARM/RISCV Kefeng Wang
2021-01-15 5:46 ` [PATCH v3 1/4] initrd: Add the preprocessor guard in initrd.h Kefeng Wang
2021-01-15 5:46 ` [PATCH v3 2/4] initramfs: Provide a common initrd reserve function Kefeng Wang
2021-01-15 5:46 ` [PATCH v3 3/4] ARM: Covert to reserve_initrd_mem() Kefeng Wang
2021-01-17 4:58 ` Kefeng Wang
2021-01-15 5:46 ` [PATCH v3 4/4] riscv: " Kefeng Wang
2021-01-17 4:57 ` [PATCH v3 0/4] initrd: Use unified initrd reserve function in ARM/RISCV Kefeng Wang
2021-01-17 10:09 ` Russell King - ARM Linux admin
[not found] ` <cc47f8cf-8778-43ab-77de-9dd220de7c26@huawei.com>
2021-01-18 9:17 ` Russell King - ARM Linux admin [this message]
2021-01-22 7:29 ` Kefeng Wang
2021-01-22 3:54 ` Palmer Dabbelt
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=20210118091733.GD1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=atish.patra@wdc.com \
--cc=guoren@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=palmerdabbelt@google.com \
--cc=paul.walmsley@sifive.com \
--cc=wangkefeng.wang@huawei.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;
as well as URLs for NNTP newsgroup(s).