mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
	<palmerdabbelt@google.com>, Atish Patra <atish.patra@wdc.com>,
	Palmer Dabbelt <palmer@dabbelt.com>, <guoren@kernel.org>,
	Paul Walmsley <paul.walmsley@sifive.com>
Subject: Re: [PATCH v3 0/4] initrd: Use unified initrd reserve function in ARM/RISCV
Date: Fri, 22 Jan 2021 15:29:43 +0800	[thread overview]
Message-ID: <d911b1e6-ed0d-4a73-aee4-060b957897f8@huawei.com> (raw)
In-Reply-To: <20210118091733.GD1551@shell.armlinux.org.uk>


On 2021/1/18 17:17, Russell King - ARM Linux admin wrote:
> 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.

ok,thank you for letting me know that the email has been received,

any comment about the ARM part in the patchset  ;)

>
> 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.
>

  reply	other threads:[~2021-01-22  7:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15  5:46 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
2021-01-22  7:29         ` Kefeng Wang [this message]
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=d911b1e6-ed0d-4a73-aee4-060b957897f8@huawei.com \
    --to=wangkefeng.wang@huawei.com \
    --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=linux@armlinux.org.uk \
    --cc=palmer@dabbelt.com \
    --cc=palmerdabbelt@google.com \
    --cc=paul.walmsley@sifive.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

all inboxes | Powered by JetHome®