public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Jan Kara <jack@suse.cz>, "yukuai (C)" <yukuai3@huawei.com>
Cc: paolo.valente@linaro.org, tj@kernel.org,
	linux-block@vger.kernel.org, cgroups@vger.kernel.org,
	linux-kernel@vger.kernel.org, yi.zhang@huawei.com
Subject: Re: [PATCH -next v5 0/3] support concurrent sync io for bfq on a specail occasion
Date: Mon, 23 May 2022 06:36:58 -0600	[thread overview]
Message-ID: <25f6703e-9e10-75d9-a893-6df1e6b75254@kernel.dk> (raw)
In-Reply-To: <20220523085902.wmxoebyq3crerecr@quack3.lan>

On 5/23/22 2:59 AM, Jan Kara wrote:
> On Mon 23-05-22 09:10:38, yukuai (C) wrote:
>> ? 2022/05/21 20:21, Jens Axboe ??:
>>> On 5/21/22 1:22 AM, yukuai (C) wrote:
>>>> ? 2022/05/14 17:29, yukuai (C) ??:
>>>>> ? 2022/05/05 9:00, yukuai (C) ??:
>>>>>> Hi, Paolo
>>>>>>
>>>>>> Can you take a look at this patchset? It has been quite a long time
>>>>>> since we spotted this problem...
>>>>>>
>>>>>
>>>>> friendly ping ...
>>>> friendly ping ...
>>>
>>> I can't speak for Paolo, but I've mentioned before that the majority
>>> of your messages end up in my spam. That's still the case, in fact
>>> I just marked maybe 10 of them as not spam.
>>>
>>> You really need to get this issued sorted out, or you will continue
>>> to have patches ignore because folks may simply not see them.
>>>
>> Hi,
>>
>> Thanks for your notice.
>>
>> Is it just me or do you see someone else's messages from *huawei.com
>> end up in spam? I tried to seek help from our IT support, however, they
>> didn't find anything unusual...
> 
> So actually I have noticed that a lot of (valid) email from huawei.com (not
> just you) ends up in the spam mailbox. For me direct messages usually pass
> (likely matching SPF records for originating mail server save the email
> from going to spam) but messages going through mailing lists are flagged as
> spam because the emails are missing valid DKIM signature but huawei.com
> DMARC config says there should be DKIM signature (even direct messages are
> missing DKIM so this does not seem as a mailing list configuration issue).
> So this seems as some misconfiguration of the mails on huawei.com side
> (likely missing DKIM signing of outgoing email).

SPF/DKIM was indeed a problem earlier for yukaui patches, but I don't
see that anymore. Maybe it's still an issue for some emails, from them
or Huawei in general?

-- 
Jens Axboe


  reply	other threads:[~2022-05-23 12:37 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28 12:08 [PATCH -next v5 0/3] support concurrent sync io for bfq on a specail occasion Yu Kuai
2022-04-28 12:08 ` [PATCH -next v5 1/3] block, bfq: record how many queues are busy in bfq_group Yu Kuai
2022-04-28 12:45   ` Jan Kara
2022-04-28 12:08 ` [PATCH -next v5 2/3] block, bfq: refactor the counting of 'num_groups_with_pending_reqs' Yu Kuai
2022-04-28 12:08 ` [PATCH -next v5 3/3] block, bfq: do not idle if only one group is activated Yu Kuai
2022-05-05  1:00 ` [PATCH -next v5 0/3] support concurrent sync io for bfq on a specail occasion yukuai (C)
2022-05-14  9:29   ` yukuai (C)
2022-05-21  7:22     ` yukuai (C)
2022-05-21 12:21       ` Jens Axboe
2022-05-23  1:10         ` yukuai (C)
2022-05-23  1:24           ` Jens Axboe
2022-05-23  8:18             ` Yu Kuai
2022-05-23 12:36               ` Jens Axboe
2022-05-23 12:58                 ` Yu Kuai
2022-05-23 13:29                   ` Jens Axboe
2022-05-23  8:59           ` Jan Kara
2022-05-23 12:36             ` Jens Axboe [this message]
2022-05-23 15:25               ` Jan Kara
2022-05-24  1:13                 ` Yu Kuai
2022-06-01  6:16                   ` Jens Axboe
2022-06-01  7:19                     ` Yu Kuai
2022-06-07  3:10                 ` Yu Kuai
2022-06-07  9:54                   ` Jan Kara
2022-06-07 11:51                     ` Yu Kuai
2022-06-07 13:06                       ` Yu Kuai
2022-06-07 20:30                         ` Jan Kara

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=25f6703e-9e10-75d9-a893-6df1e6b75254@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=cgroups@vger.kernel.org \
    --cc=jack@suse.cz \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paolo.valente@linaro.org \
    --cc=tj@kernel.org \
    --cc=yi.zhang@huawei.com \
    --cc=yukuai3@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