diff for duplicates of <20190510121720.GT2589@hirez.programming.kicks-ass.net> diff --git a/a/1.txt b/N1/1.txt index 38be379..afff634 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,4 +1,4 @@ -On Fri, May 10, 2019 at 12:21:03PM +0900, Masami Hiramatsu wrote: +On Fri, May 10, 2019@12:21:03PM +0900, Masami Hiramatsu wrote: > Yes, optprobe also has to save and restore the flags. > Above trampline is for kretprobe, which is placed at the function return, so > we don't have to care about flags. diff --git a/a/content_digest b/N1/content_digest index 5e29c72..4e7ef36 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -8,12 +8,12 @@ "ref\081170F0B-A2BB-4CD6-A1B5-5E7E0DDBC282@amacapital.net\0" "ref\020190509174316.pzuakeu657g3fnlm@home.goodmis.org\0" "ref\020190510122103.5a7bc5416b7af96b27d4fab4@kernel.org\0" - "From\0peterz at infradead.org (Peter Zijlstra)\0" + "From\0peterz@infradead.org (Peter Zijlstra)\0" "Subject\0[PATCH 2/4] x86/kprobes: Fix frame pointer annotations\0" "Date\0Fri, 10 May 2019 14:17:20 +0200\0" "\00:1\0" "b\0" - "On Fri, May 10, 2019 at 12:21:03PM +0900, Masami Hiramatsu wrote:\n" + "On Fri, May 10, 2019@12:21:03PM +0900, Masami Hiramatsu wrote:\n" "> Yes, optprobe also has to save and restore the flags.\n" "> Above trampline is for kretprobe, which is placed at the function return, so\n" "> we don't have to care about flags.\n" @@ -24,4 +24,4 @@ "But both ftrace and retprobes are at C function call boundaries.\n" Preserving flags doesn't make sense. -e11798948c2a850e64b4c64ae43acea88c0a94d8c35bd37d19bd8ceec213295b +e694fa69898023f61866117136f1731f299282a78fbe01928e966256be4207b8
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox