[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <924169bb-4a94-e9b1-1aeb-86c99e8637e7@acm.org>
Date: Sat, 9 Apr 2022 14:31:09 -0700
From: Bart Van Assche <bvanassche@....org>
To: Jens Axboe <axboe@...nel.dk>, "yukuai (C)" <yukuai3@...wei.com>,
andriy.shevchenko@...ux.intel.com, john.garry@...wei.com,
ming.lei@...hat.com
Cc: linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
yi.zhang@...wei.com
Subject: Re: [PATCH -next RFC v2 0/8] improve tag allocation under heavy load
On 4/8/22 19:28, Jens Axboe wrote:
> The easiest is probably to try and send patches to a gmail account. If
> you don't have one, just create one. That will help you see the issue
> and verify whatever the fix might be. It might be a company email
> server issue, hower.
Hi Jens and Yu,
I think it's a company email issue. Many servers that receive email rely
on the SPF, DKIM & DMARC standards to determine whether or not to
classify email as spam. I had to add the following rule to my inbox
receive Huawei.com emails:
Matches: from:(huawei.com)
Do this: Never send it to Spam
Thanks,
Bart.
Powered by blists - more mailing lists