Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Zheng Yejian <zhengyejian1@huawei.com>
Cc: rostedt@goodmis.org, stable@vger.kernel.org
Subject: Re: [PATCH 5.10 0/2] re: FAILED: patch "[PATCH] ftrace: Fix possible
Date: Mon, 24 Jul 2023 08:32:02 +0200	[thread overview]
Message-ID: <2023072456-stillness-duvet-4d1f@gregkh> (raw)
In-Reply-To: <20230724022924.3478612-1-zhengyejian1@huawei.com>

On Mon, Jul 24, 2023 at 10:29:22AM +0800, Zheng Yejian wrote:
> Resolve backport failed due to lack of dependency commit
> db42523b4f3e ("ftrace: Store the order of pages allocated in ftrace_page")
> 
> Linus Torvalds (1):
>   ftrace: Store the order of pages allocated in ftrace_page
> 
> Zheng Yejian (1):
>   ftrace: Fix possible warning on checking all pages used in
>     ftrace_process_locs()
> 
>  kernel/trace/ftrace.c | 72 ++++++++++++++++++++++++++-----------------
>  1 file changed, 44 insertions(+), 28 deletions(-)
> 
> -- 
> 2.25.1
> 

Both now queued up, thanks.

greg k-h

      parent reply	other threads:[~2023-07-24  6:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-21 14:24 FAILED: patch "[PATCH] ftrace: Fix possible warning on checking all pages used in" failed to apply to 5.10-stable tree gregkh
2023-07-24  2:29 ` [PATCH 5.10 0/2] re: FAILED: patch "[PATCH] ftrace: Fix possible Zheng Yejian
2023-07-24  2:29   ` [PATCH 5.10 1/2] ftrace: Store the order of pages allocated in ftrace_page Zheng Yejian
2023-07-24  2:29   ` [PATCH 5.10 2/2] ftrace: Fix possible warning on checking all pages used in ftrace_process_locs() Zheng Yejian
2023-07-24  6:32   ` Greg KH [this message]

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=2023072456-stillness-duvet-4d1f@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=rostedt@goodmis.org \
    --cc=stable@vger.kernel.org \
    --cc=zhengyejian1@huawei.com \
    /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