Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Krishanth Jagaduri via B4 Relay
	<devnull+Krishanth.Jagaduri.sony.com@kernel.org>,
	Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH] Documentation/no_hz: Remove description that states boot CPU cannot be nohz_full
Date: Fri,  7 Feb 2025 17:51:11 -0500	[thread overview]
Message-ID: <20250207163329-66b9c636007be548@stable.kernel.org> (raw)
In-Reply-To: <20250205-send-oss-20250129-v1-1-d404921e6d7e@sony.com>

[ Sasha's backport helper bot ]

Hi,

The upstream commit SHA1 provided is correct: 5097cbcb38e6e0d2627c9dde1985e91d2c9f880e

WARNING: Author mismatch between patch and upstream commit:
Backport author: Krishanth Jagaduri via B4 Relay<devnull+Krishanth.Jagaduri.sony.com@kernel.org>
Commit author: Oleg Nesterov<oleg@redhat.com>


Status in newer kernel trees:
6.13.y | Present (exact SHA1)

Note: The patch differs from the upstream commit:
---
Failed to apply patch cleanly, falling back to interdiff...
---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.13.y       |  Failed     |  N/A       |
| stable/linux-6.12.y       |  Failed     |  N/A       |
| stable/linux-6.6.y        |  Success    |  Failed    |
| stable/linux-6.1.y        |  Success    |  Failed    |
| stable/linux-5.15.y       |  Success    |  Failed    |
| stable/linux-5.10.y       |  Success    |  Failed    |
| stable/linux-5.4.y        |  Success    |  Failed    |

Build Errors:
Build error for stable/linux-6.6.y:
    ssh: connect to host 192.168.1.58 port 22: No route to host

Build error for stable/linux-6.1.y:
    ssh: connect to host 192.168.1.58 port 22: No route to host

Build error for stable/linux-5.15.y:
    ssh: connect to host 192.168.1.58 port 22: No route to host

Build error for stable/linux-5.10.y:
    ssh: connect to host 192.168.1.58 port 22: No route to host

Build error for stable/linux-5.4.y:
    ssh: connect to host 192.168.1.58 port 22: No route to host

      parent reply	other threads:[~2025-02-07 22:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05  3:02 [PATCH] Documentation/no_hz: Remove description that states boot CPU cannot be nohz_full Krishanth Jagaduri via B4 Relay
2025-02-05  9:18 ` Greg KH
2025-02-06  9:49   ` Krishanth Jagaduri
2025-02-07 22:51 ` Sasha Levin [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=20250207163329-66b9c636007be548@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=devnull+Krishanth.Jagaduri.sony.com@kernel.org \
    --cc=stable@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