All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, chao@kernel.org
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 2/2] f2fs: sysfs: export linear_lookup in features directory
Date: Wed, 25 Jun 2025 10:09:03 -0400	[thread overview]
Message-ID: <20250624190110-7be094696d09ba0e@stable.kernel.org> (raw)
In-Reply-To: <20250416054805.1416834-2-chao@kernel.org>

[ Sasha's backport helper bot ]

Hi,

Summary of potential issues:
ℹ️ This is part 2/2 of a series
⚠️ Found matching upstream commit but patch is missing proper reference to it

Found matching upstream commit: 617e0491abe4d8d45c5110ca474c0feb428e6828

Note: The patch differs from the upstream commit:
---
1:  617e0491abe4d ! 1:  4c702e18f9b37 f2fs: sysfs: export linear_lookup in features directory
    @@ Commit message
         supported
     
         Signed-off-by: Chao Yu <chao@kernel.org>
    -    Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
     
      ## Documentation/ABI/testing/sysfs-fs-f2fs ##
     @@ Documentation/ABI/testing/sysfs-fs-f2fs: Description:	Shows all enabled kernel features.
---

NOTE: These results are for this patch alone. Full series testing will be
performed when all parts are received.

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.4.y        |  Success    |  Success   |

  reply	other threads:[~2025-06-25 14:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-16  5:48 [f2fs-dev] [PATCH 1/2] f2fs: sysfs: add encoding_flags entry Chao Yu via Linux-f2fs-devel
2025-04-16  5:48 ` Chao Yu
2025-04-16  5:48 ` [f2fs-dev] [PATCH 2/2] f2fs: sysfs: export linear_lookup in features directory Chao Yu via Linux-f2fs-devel
2025-04-16  5:48   ` Chao Yu
2025-06-25 14:09   ` Sasha Levin [this message]
2025-04-28 22:40 ` [f2fs-dev] [PATCH 1/2] f2fs: sysfs: add encoding_flags entry patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-04-28 22:40   ` patchwork-bot+f2fs
2025-06-24 10:00 ` [f2fs-dev] [STABLE 5.15+] " Lee Jones via Linux-f2fs-devel
2025-06-24 10:00   ` Lee Jones
2025-07-02 10:20   ` [f2fs-dev] " Greg Kroah-Hartman
2025-07-02 10:20     ` Greg Kroah-Hartman
2025-07-23  8:26     ` [f2fs-dev] " Lee Jones via Linux-f2fs-devel
2025-07-23  8:26       ` Lee Jones
2025-07-23  9:41       ` [f2fs-dev] " Greg Kroah-Hartman
2025-07-23  9:41         ` Greg Kroah-Hartman
2025-07-24 10:18         ` [f2fs-dev] " Lee Jones via Linux-f2fs-devel
2025-07-24 10:18           ` Lee Jones
2025-06-25 14:07 ` [PATCH 1/2] " Sasha Levin

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=20250624190110-7be094696d09ba0e@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=chao@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.