linux-kernel - Re: [PATCH v2 2/3] io_uring: minor clean up in trace events definition

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 16 Jun 2021 14:53:55 +0100
From:   Pavel Begunkov <asml.silence@...il.com>
To:     Olivier Langlois <olivier@...llion01.com>,
        Jens Axboe <axboe@...nel.dk>,
        Steven Rostedt <rostedt@...dmis.org>,
        Ingo Molnar <mingo@...hat.com>, io-uring@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/3] io_uring: minor clean up in trace events
 definition

On 6/16/21 2:33 PM, Olivier Langlois wrote:
> On Tue, 2021-06-15 at 15:50 -0600, Jens Axboe wrote:
>> On 6/15/21 3:48 AM, Pavel Begunkov wrote:
>>> On 5/31/21 7:54 AM, Olivier Langlois wrote:
>>>> Fix tabulation to make nice columns
>>>
>>> Reviewed-by: Pavel Begunkov <asml.silence@...il.com>
>>
>> I don't have any of the original 1-3 patches, and don't see them on the
>> list either. I'd love to apply for 5.14, but...
>>
>> Olivier, are you getting any errors sending these out?Usually I'd
>> expect
>> them in my inbox as well outside of the list, but they don't seem to
>> have
>> arrived there either.
>>
>> In any case, please resend. As Pavel mentioned, a cover letter is
>> always
>> a good idea for a series of more than one patch.
>>
> I do not get any errors but I have noticed too that my emails weren't
> accepted by the lists.
> 
> They will accept replies in already existing threads but they won't let
> me create new ones. ie: accepting my patches.
> 
> I'll learn how create a cover email and I will resend the series of
> patches later today.

"--cover-letter" to "git format-patch" will create a cover template
to fill in. Depends on patches, but can be a small description of the
series.

Regarding resending, Jens already took/applied them today, see
a reply to 1/3. You can find them queued at

https://git.kernel.dk/cgit/linux-block/log/?h=for-5.14/io_uring

> one thing that I can tell, it is that Pavel and you are always
> recipients along with the lists for my patches... So you should have a
> private copy somewhere in your mailbox...
> 
> The other day, I even got this:
> -------- Forwarded Message --------
> From: Mail Delivery System <Mailer-Daemon@...ud48395.mywhc.ca>
> To: olivier@...llion01.com
> Subject: Mail delivery failed: returning message to sender
> Date: Thu, 10 Jun 2021 11:38:51 -0400
> 
> This message was created automatically by mail delivery software.
> 
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es)
> failed:
> 
>   linux-kernel@...r.kernel.org
>     host vger.kernel.org [23.128.96.18]
>     SMTP error from remote mail server after end of data:
>     550 5.7.1 Content-Policy accept-into-freezer-1 msg:
>     Bayes Statistical Bogofilter considers this message SPAM.  BF:<S
> 0.9924>  In case you disagree, send the ENTIRE message plus this error
> message to <postmaster@...r.kernel.org> ; S230153AbhFJPkq
>   io-uring@...r.kernel.org
>     host vger.kernel.org [23.128.96.18]
>     SMTP error from remote mail server after end of data:
>     550 5.7.1 Content-Policy accept-into-freezer-1 msg:
>     Bayes Statistical Bogofilter considers this message SPAM.  BF:<S
> 0.9924>  In case you disagree, send the ENTIRE message plus this error
> message to <postmaster@...r.kernel.org> ; S230153AbhFJPkq
> 
> There is definitely something that the list software doesn't like in my
> emails but I don't know what...
> 
> I did send an email to postmaster@...r.kernel.org to tell them about
> the problem but I didn't hear back anything from the postmaster... (My
> email probably went to the SPAM folder as well!)
> 

-- 
Pavel Begunkov