All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1.y 2/5] erofs: sunset erofs_dbg()
Date: Wed, 23 Jul 2025 00:34:04 -0400	[thread overview]
Message-ID: <1753229137-64ac7036@stable.kernel.org> (raw)
In-Reply-To: <20250722100029.3052177-3-hsiangkao@linux.alibaba.com>

[ Sasha's backport helper bot ]

Hi,

✅ All tests passed successfully. No issues detected.
No action required from the submitter.

The upstream commit SHA1 provided is correct: 10656f9ca60ed85f4cfc06bcbe1f240ee310fa8c

Status in newer kernel trees:
6.15.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (exact SHA1)

Note: The patch differs from the upstream commit:
---
1:  10656f9ca60e ! 1:  490c3ffa300c erofs: sunset erofs_dbg()
    @@ Metadata
      ## Commit message ##
         erofs: sunset erofs_dbg()
     
    +    commit 10656f9ca60ed85f4cfc06bcbe1f240ee310fa8c upstream.
    +
         Such debug messages are rarely used now.  Let's get rid of these,
         and revert locally if they are needed for debugging.
     

---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| 6.1                       | Success     | Success    |

  reply	other threads:[~2025-07-23  4:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-22 10:00 [PATCH 6.1.y 0/5] erofs: backport for `erofs: address D-cache aliasing` Gao Xiang
2025-07-22 10:00 ` [PATCH 6.1.y 1/5] erofs: get rid of debug_one_dentry() Gao Xiang
2025-07-23  4:34   ` Sasha Levin
2025-07-30  8:55   ` Patch "erofs: get rid of debug_one_dentry()" has been added to the 6.1-stable tree gregkh
2025-07-22 10:00 ` [PATCH 6.1.y 2/5] erofs: sunset erofs_dbg() Gao Xiang
2025-07-23  4:34   ` Sasha Levin [this message]
2025-07-30  8:55   ` Patch "erofs: sunset erofs_dbg()" has been added to the 6.1-stable tree gregkh
2025-07-22 10:00 ` [PATCH 6.1.y 3/5] erofs: drop z_erofs_page_mark_eio() Gao Xiang
2025-07-23  4:34   ` Sasha Levin
2025-07-30  8:55   ` Patch "erofs: drop z_erofs_page_mark_eio()" has been added to the 6.1-stable tree gregkh
2025-07-22 10:00 ` [PATCH 6.1.y 4/5] erofs: simplify z_erofs_transform_plain() Gao Xiang
2025-07-23  4:34   ` Sasha Levin
2025-07-30  8:55   ` Patch "erofs: simplify z_erofs_transform_plain()" has been added to the 6.1-stable tree gregkh
2025-07-22 10:00 ` [PATCH 6.1.y 5/5] erofs: address D-cache aliasing Gao Xiang
2025-07-23  4:34   ` Sasha Levin
2025-07-30  8:55   ` Patch "erofs: address D-cache aliasing" has been added to the 6.1-stable tree gregkh

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=1753229137-64ac7036@stable.kernel.org \
    --to=sashal@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 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.