linux-csky.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Punit Agrawal <punitagrawal@gmail.com>
Cc: naveen.n.rao@linux.ibm.com, anil.s.keshavamurthy@intel.com,
	davem@davemloft.net, linux-kernel@vger.kernel.org,
	guoren@kernel.org, linux-csky@vger.kernel.org,
	x86@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v2 0/5] kprobes: Bugfix and improvements
Date: Wed, 28 Jul 2021 08:39:13 +0900	[thread overview]
Message-ID: <20210728083913.bcf0fa991e4a2b819f457543@kernel.org> (raw)
In-Reply-To: <20210727133426.2919710-1-punitagrawal@gmail.com>

Hi Punit,

Thanks for resending this series.

Ingo, could you pick this patch too?
I'll resend my series on this series. 

Thank you,

On Tue, 27 Jul 2021 22:34:21 +0900
Punit Agrawal <punitagrawal@gmail.com> wrote:

> Hi,
> 
> This is the second posting of patches previously posted at
> [0]. Although the patches were reviewed / acked in the previous cycle
> but for some didn't end up getting picked up for this cycle.
> 
> This posting rebases the patches to 5.14-rc3 and makes some minor
> improvements to the commit log in Patch 1. I've also added the tags as
> appropriate from the previous posting.
> 
> It would be great if the patches can be picked up this time around.
> 
> Thanks,
> Punit
> 
> 
> [0] https://lore.kernel.org/linux-csky/20210609105019.3626677-1-punitagrawal@gmail.com/
> 
> Punit Agrawal (5):
>   kprobes: Do not use local variable when creating debugfs file
>   kprobes: Use helper to parse boolean input from userspace
>   kprobe: Simplify prepare_kprobe() by dropping redundant version
>   csky: ftrace: Drop duplicate implementation of
>     arch_check_ftrace_location()
>   kprobes: Make arch_check_ftrace_location static
> 
>  arch/csky/kernel/probes/ftrace.c |  7 ----
>  include/linux/kprobes.h          |  7 ++--
>  kernel/kprobes.c                 | 58 ++++++++++----------------------
>  3 files changed, 23 insertions(+), 49 deletions(-)
> 
> -- 
> 2.30.2
> 


-- 
Masami Hiramatsu <mhiramat@kernel.org>

  parent reply	other threads:[~2021-07-27 23:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-27 13:34 [PATCH v2 0/5] kprobes: Bugfix and improvements Punit Agrawal
2021-07-27 13:34 ` [PATCH v2 1/5] kprobes: Do not use local variable when creating debugfs file Punit Agrawal
2021-07-27 13:34 ` [PATCH v2 2/5] kprobes: Use helper to parse boolean input from userspace Punit Agrawal
2021-07-27 13:34 ` [PATCH v2 3/5] kprobe: Simplify prepare_kprobe() by dropping redundant version Punit Agrawal
2021-07-27 13:34 ` [PATCH v2 4/5] csky: ftrace: Drop duplicate implementation of arch_check_ftrace_location() Punit Agrawal
2021-07-28  0:50   ` Guo Ren
2021-07-27 13:34 ` [PATCH v2 5/5] kprobes: Make arch_check_ftrace_location static Punit Agrawal
2021-07-27 23:39 ` Masami Hiramatsu [this message]
2021-08-17 12:07   ` [PATCH v2 0/5] kprobes: Bugfix and improvements Punit Agrawal

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=20210728083913.bcf0fa991e4a2b819f457543@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=anil.s.keshavamurthy@intel.com \
    --cc=davem@davemloft.net \
    --cc=guoren@kernel.org \
    --cc=linux-csky@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=naveen.n.rao@linux.ibm.com \
    --cc=peterz@infradead.org \
    --cc=punitagrawal@gmail.com \
    --cc=x86@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;
as well as URLs for NNTP newsgroup(s).