From: Sahil <sahilcdq0@gmail.com>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: jonas@southpole.se, stefan.kristiansson@saunalahti.fi,
shorne@gmail.com, naveen@kernel.org, davem@davemloft.net,
pjw@kernel.org, wangruikang@iscas.ac.cn, namcao@linutronix.de,
kees@kernel.org, linux-openrisc@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/4] openrisc: Add support for KProbes and Kretprobes
Date: Fri, 13 Nov 2026 22:52:25 +0530 [thread overview]
Message-ID: <2f9cd058-c2a2-4a7f-a755-a66653a8f659@gmail.com> (raw)
In-Reply-To: <undine-1794560694824423564-2986102e2a604795@undined.local>
Hi Masami,
On 11/13/26 2:34 PM, Masami Hiramatsu (Google) wrote:
> Hi Sahil,
>
> Can you update the series according to the Sashiko's comment[1]?
>
> [1] https://sashiko.dev/#/patchset/20261026201240.107462-3-sahilcdq0%40gmail.com
Sure, I'll make those changes along with the ones suggested by Stafford.
> Also, can you check your git email settings, so that the next
> version does *NOT* reply to the previous version.
>
> This mail has
>
> Message-ID: <20261026201240.107462-1-sahilcdq0@gmail.com>
> X-Mailer: git-send-email 2.55.0
> In-Reply-To: <20260930202744.50489-1-sahilcdq0@gmail.com>
> References: <20260930202744.50489-1-sahilcdq0@gmail.com>
>
> But I can not find "20260930202744.50489-1-sahilcdq0@gmail.com" in
> the LKML archive.
>
> Also "[PATCH v3 2/4] openrisc: Add KProbes" has
>
> Message-ID: <20261026201240.107462-3-sahilcdq0@gmail.com>
> X-Mailer: git-send-email 2.55.0
> In-Reply-To: <20260930202744.50489-1-sahilcdq0@gmail.com>
> References: <20260930202744.50489-1-sahilcdq0@gmail.com>
>
> This should be in reply to the cover mail
> "20261026201240.107462-1-sahilcdq0@gmail.com"
Oh, that's weird. Maybe I used the wrong message-id when setting "in-reply-to"
using git-send-email. I'll send the next series such that it doesn't reply to
the previous version.
>
> Thank you,
Thanks,
Sahil
next prev parent reply other threads:[~2026-11-13 17:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260930202744.50489-1-sahilcdq0@gmail.com>
2026-10-26 20:12 ` Sahil Siddiq
2026-11-13 9:04 ` Masami Hiramatsu (Google)
2026-11-13 17:22 ` Sahil [this message]
2026-10-26 20:12 ` [PATCH v3 1/4] openrisc: Add utilities and clean up simulation of instructions Sahil Siddiq
2026-11-07 6:45 ` Stafford Horne
2026-11-13 17:11 ` Sahil
2026-10-26 20:12 ` [PATCH v3 2/4] openrisc: Add KProbes Sahil Siddiq
2026-10-26 20:26 ` Sahil
2026-11-08 7:46 ` Stafford Horne
2026-11-13 17:13 ` Sahil
2026-10-26 20:12 ` [PATCH v3 3/4] openrisc: Add unit tests for KProbes on branch instructions Sahil Siddiq
2026-11-08 8:03 ` Stafford Horne
2026-11-13 17:15 ` Sahil
2026-10-26 20:12 ` [PATCH v3 4/4] openrisc: Add Kretprobes Sahil Siddiq
2026-11-08 7:58 ` Stafford Horne
2026-11-13 17:16 ` Sahil
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=2f9cd058-c2a2-4a7f-a755-a66653a8f659@gmail.com \
--to=sahilcdq0@gmail.com \
--cc=davem@davemloft.net \
--cc=jonas@southpole.se \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-openrisc@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=namcao@linutronix.de \
--cc=naveen@kernel.org \
--cc=pjw@kernel.org \
--cc=shorne@gmail.com \
--cc=stefan.kristiansson@saunalahti.fi \
--cc=wangruikang@iscas.ac.cn \
/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
all inboxes | Powered by JetHome®