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]

Message-ID: <473dbbd3376a085df4672a30f86fe8faf8f8254a.camel@trillion01.com>
Date:   Sun, 20 Jun 2021 15:15:48 -0400
From:   Olivier Langlois <olivier@...llion01.com>
To:     Jens Axboe <axboe@...nel.dk>, Steven Rostedt <rostedt@...dmis.org>
Cc:     Pavel Begunkov <asml.silence@...il.com>,
        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 Wed, 2021-06-16 at 15:33 -0600, Jens Axboe wrote:
> On 6/16/21 3:30 PM, Olivier Langlois wrote:
> > 
> 
> > My take away from all this is that it is very important that my
> > patches
> > do reach the lists and I commit to put the necessary efforts to
> > make
> > that happen.
> 
> Yes. Both for tooling, but also so that non-cc'ed people see it and
> can
> reply.
> 
> > My last email was simply myself starting diagnose where my problem
> > could be outloud.
> > 
> > Steven did mention that he wasn't seeing the Message-Id field in my
> > patch emails. I'm very grateful for this clue!
> > 
> > My main email client is Gnome Evolution (when Message-Id is present
> > in
> > my mails) and I do the following to send out patches:
> > 
> > 1. git format-patch -o ~/patches HEAD^
> > 2. Edit patch file by adding recipients listed by
> > scripts/get_maintainer.pl
> > 3. cat patch_file | msmtp -t -a default
> 
> Why not just use git send-email? That's literally what that is for.
> It's
> what I use to send out patches.
> 
> 
> 
I found my problem. I had to add the option --thread to git format-
patch

as in:
$ git format-patch --thread -o ~/patches HEAD^