[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2DD82DF9-3409-43E9-957D-CB296E3FD7D6@vmware.com>
Date: Mon, 30 Jan 2023 06:43:33 +0000
From: Nadav Amit <namit@...are.com>
To: Ajay Kaher <akaher@...are.com>
CC: Steven Rostedt <rostedt@...dmis.org>,
"mhiramat@...nel.org" <mhiramat@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-trace-kernel@...r.kernel.org"
<linux-trace-kernel@...r.kernel.org>,
"chinglinyu@...gle.com" <chinglinyu@...gle.com>,
Srivatsa Bhat <srivatsab@...are.com>,
"srivatsa@...il.mit.edu" <srivatsa@...il.mit.edu>,
Alexey Makhalov <amakhalov@...are.com>,
Vasavi Sirnapalli <vsirnapalli@...are.com>,
Tapas Kundu <tkundu@...are.com>,
"er.ajay.kaher@...il.com" <er.ajay.kaher@...il.com>
Subject: Re: [PATCH 0/8] tracing: introducing eventfs
> On Jan 29, 2023, at 8:07 PM, Ajay Kaher <akaher@...are.com> wrote:
>
>> Hi Ajay,
>>
>> Thanks a lot for sending these out.
>>
>> Note, something went wrong with your threading, as all the patches should
>> be a reply to this one, but instead, they all (including this email) are a
>> reply to patch 1 ??
>
> Not sure why this is happenning, but I will try to fix in v2.
I suspect it happens since you create the cover letter manually.
If that is the case, instead use 'git format-patch --cover-letter …’.
Powered by blists - more mailing lists