From: Atul Kumar Pant <atulpant.linux@gmail.com>
To: naveen.n.rao@linux.ibm.com, anil.s.keshavamurthy@intel.com,
davem@davemloft.net, mhiramat@kernel.org
Cc: shuah@kernel.org, linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v1] samples: kprobes: Fixes a typo
Date: Sat, 7 Oct 2023 21:09:00 +0530 [thread overview]
Message-ID: <20231007153900.GA20160@atom0118> (raw)
In-Reply-To: <20230923173040.GA159038@atom0118>
On Sat, Sep 23, 2023 at 11:00:46PM +0530, Atul Kumar Pant wrote:
> On Thu, Aug 17, 2023 at 10:38:19PM +0530, Atul Kumar Pant wrote:
> > Fixes typo in a function name.
> >
> > Signed-off-by: Atul Kumar Pant <atulpant.linux@gmail.com>
> > ---
> > samples/kprobes/kretprobe_example.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/samples/kprobes/kretprobe_example.c b/samples/kprobes/kretprobe_example.c
> > index cbf16542d84e..ed79fd3d48fb 100644
> > --- a/samples/kprobes/kretprobe_example.c
> > +++ b/samples/kprobes/kretprobe_example.c
> > @@ -35,7 +35,7 @@ struct my_data {
> > ktime_t entry_stamp;
> > };
> >
> > -/* Here we use the entry_hanlder to timestamp function entry */
> > +/* Here we use the entry_handler to timestamp function entry */
> > static int entry_handler(struct kretprobe_instance *ri, struct pt_regs *regs)
> > {
> > struct my_data *data;
> > --
> > 2.25.1
> >
>
> Hi all, can someone provide comments on this change.
Hi all, can someone please review this change. It has been not
reviewed for quite some time.
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
WARNING: multiple messages have this Message-ID (diff)
From: Atul Kumar Pant <atulpant.linux@gmail.com>
To: naveen.n.rao@linux.ibm.com, anil.s.keshavamurthy@intel.com,
davem@davemloft.net, mhiramat@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org, shuah@kernel.org
Subject: Re: [PATCH v1] samples: kprobes: Fixes a typo
Date: Sat, 7 Oct 2023 21:09:00 +0530 [thread overview]
Message-ID: <20231007153900.GA20160@atom0118> (raw)
In-Reply-To: <20230923173040.GA159038@atom0118>
On Sat, Sep 23, 2023 at 11:00:46PM +0530, Atul Kumar Pant wrote:
> On Thu, Aug 17, 2023 at 10:38:19PM +0530, Atul Kumar Pant wrote:
> > Fixes typo in a function name.
> >
> > Signed-off-by: Atul Kumar Pant <atulpant.linux@gmail.com>
> > ---
> > samples/kprobes/kretprobe_example.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/samples/kprobes/kretprobe_example.c b/samples/kprobes/kretprobe_example.c
> > index cbf16542d84e..ed79fd3d48fb 100644
> > --- a/samples/kprobes/kretprobe_example.c
> > +++ b/samples/kprobes/kretprobe_example.c
> > @@ -35,7 +35,7 @@ struct my_data {
> > ktime_t entry_stamp;
> > };
> >
> > -/* Here we use the entry_hanlder to timestamp function entry */
> > +/* Here we use the entry_handler to timestamp function entry */
> > static int entry_handler(struct kretprobe_instance *ri, struct pt_regs *regs)
> > {
> > struct my_data *data;
> > --
> > 2.25.1
> >
>
> Hi all, can someone provide comments on this change.
Hi all, can someone please review this change. It has been not
reviewed for quite some time.
next prev parent reply other threads:[~2023-10-07 15:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 17:08 [PATCH v1] samples: kprobes: Fixes a typo Atul Kumar Pant
2023-08-17 17:08 ` Atul Kumar Pant
2023-09-23 17:30 ` Atul Kumar Pant
2023-09-23 17:30 ` Atul Kumar Pant
2023-10-07 15:39 ` Atul Kumar Pant [this message]
2023-10-07 15:39 ` Atul Kumar Pant
2023-10-09 13:51 ` Steven Rostedt
2023-10-09 13:51 ` Steven Rostedt
2023-10-09 15:03 ` Masami Hiramatsu
2023-10-09 15:03 ` Masami Hiramatsu
2023-10-11 18:04 ` Atul Kumar Pant
2023-10-11 18:04 ` Atul Kumar Pant
2023-10-11 18:02 ` Atul Kumar Pant
2023-10-11 18:02 ` Atul Kumar Pant
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=20231007153900.GA20160@atom0118 \
--to=atulpant.linux@gmail.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=davem@davemloft.net \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=shuah@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.