Messages in this thread |  | | Subject | Re: [PATCH -next RFC v2 0/8] improve tag allocation under heavy load | From | "yukuai (C)" <> | Date | Sat, 9 Apr 2022 15:14:02 +0800 |
| |
在 2022/04/09 10:28, Jens Axboe 写道: > On 4/8/22 8:26 PM, yukuai (C) wrote: >> 在 2022/04/09 3:10, Jens Axboe 写道: >>> For this one, and other patches you send, they send up in spam because >>> the sender can't be verified. I would encourage you to figure out what >>> is going wrong here, because a lot of your patches end up getting >>> dropped or missed because of it. >>> >> >> Hi, >> >> Thanks for your notice, however, I have no clue what is going on right >> now. I'll look for some help and hopefully that can be fixed. > > 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. >
I tried to send a patch to gmail, however, no issues are found. I am contacting our IT support and hope they can figure out what is going on.
By the way, I didn't see anything unusual for my patches in linux-block patchwork:
https://patchwork.kernel.org/project/linux-block/list/?series=&submitter=187999&state=&q=&archive=both&delegate=
Is there a seperate place to track patches?
Thanks, Kuai
|  |