public inbox for linux-f2fs-devel@lists.sourceforge.net
 help / color / mirror / Atom feed
From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: LuK1337 <priv.luk@gmail.com>, linux-f2fs-devel@lists.sourceforge.net
Cc: jaegeuk@kernel.org
Subject: Re: [f2fs-dev] [PATCH] dump.f2fs: macOS does not support lsetxattr
Date: Mon, 27 Apr 2026 15:33:36 +0800	[thread overview]
Message-ID: <5340eefd-36ee-48ee-bcfa-e5e991af6f9a@kernel.org> (raw)
In-Reply-To: <20260313130915.1752881-1-priv.luk@gmail.com>

On 3/13/26 21:09, LuK1337 wrote:
> From: Łukasz Patron <priv.luk@gmail.com>
> 
> Fixes: a66d49fd2678 ("dump.f2fs: Dump symlinks as symlinks")
> Signed-off-by: Łukasz Patron <priv.luk@gmail.com>

Reviewed-by: Chao Yu <chao@kernel.org>

Thanks,


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

      parent reply	other threads:[~2026-04-27  7:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13 13:09 [f2fs-dev] [PATCH] dump.f2fs: macOS does not support lsetxattr LuK1337
2026-04-25  9:39 ` Łukasz Patron
2026-04-27  7:33 ` Chao Yu via Linux-f2fs-devel [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=5340eefd-36ee-48ee-bcfa-e5e991af6f9a@kernel.org \
    --to=linux-f2fs-devel@lists.sourceforge.net \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=priv.luk@gmail.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