Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Gaurav Kohli <gkohli@codeaurora.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH v1] trace: Fix race in trace_open and buffer resize call
Date: Mon, 5 Oct 2020 21:59:02 +0530	[thread overview]
Message-ID: <6ebba9b9-0add-0313-3982-01031d946f44@codeaurora.org> (raw)
In-Reply-To: <20201005102745.2e49bc42@gandalf.local.home>



On 10/5/2020 7:57 PM, Steven Rostedt wrote:
> On Mon, 5 Oct 2020 10:25:15 -0400
> Steven Rostedt <rostedt@goodmis.org> wrote:
> 
>> On Mon, 5 Oct 2020 10:09:34 +0530
>> Gaurav Kohli <gkohli@codeaurora.org> wrote:
>>
>>> Hi Steven,
>>>
>>> please let us know, if below looks good to you or need modifications.
>>
>> Strange, I don't have your original email in my inbox. I do have it in my
>> LKML folder, but that's way too big for me to read. I checked my server
>> logs. I found where I received this from LKML, but there's no log that I
>> received this directly.
>>
>> How are you sending out your patches? If it doesn't land in my inbox, I'll
>> never see it.
>>
> 
> BTW, this is the second time this has happened to me. The first time I
> assumed it may have been me accidentally deleting it. Now I'm thinking it's
> on your end.
> 
> I have yet to received a patch from you directly. Last time I had to pull
> it from my LKML folder after you replied to me (letting me know you sent
> it).
> 

> -- Steve
> 

Hi Steven,

I am using normal git send-email(never saw problem with this), Not sure 
what is wrong. In my older mail i have kept you in to and rest in cc.

Let me try to resent it.

-- 
Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center,
Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.

  reply	other threads:[~2020-10-05 16:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-24 13:55 [PATCH v1] trace: Fix race in trace_open and buffer resize call Gaurav Kohli
2020-10-05  4:39 ` Gaurav Kohli
2020-10-05 14:25   ` Steven Rostedt
2020-10-05 14:27     ` Steven Rostedt
2020-10-05 16:29       ` Gaurav Kohli [this message]
2020-10-05 16:32         ` Steven Rostedt
2020-10-05 17:38           ` Gaurav Kohli
  -- strict thread matches above, loose matches on Subject: below --
2020-10-06  9:33 Gaurav Kohli
2021-01-21 14:30 ` Denis Efremov
2021-01-21 19:09   ` Steven Rostedt
2021-01-21 20:15     ` Denis Efremov
2021-01-21 20:37       ` Steven Rostedt
2021-01-22 10:59         ` Greg KH
2021-01-22 11:25           ` Gaurav Kohli
2021-01-22 14:37             ` Steven Rostedt
2021-01-23 10:49               ` Denis Efremov
2021-01-23 16:33                 ` Gaurav Kohli
2021-01-24  3:21                   ` Steven Rostedt
2021-01-24  9:57                     ` Gaurav Kohli
2021-01-24 10:05                       ` Greg KH

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=6ebba9b9-0add-0313-3982-01031d946f44@codeaurora.org \
    --to=gkohli@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=stable@vger.kernel.org \
    /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