From: Christoph Hellwig <hch@infradead.org>
To: Andrey Albershteyn <aalbersh@kernel.org>
Cc: fstests@vger.kernel.org, zlang@kernel.org
Subject: Re: [PATCH 4/4] xfstests: fix permissions on system file installed by libtoolize
Date: Tue, 22 Sep 2026 05:40:16 -0700 [thread overview]
Message-ID: <arJ3MNuF_sEs6JUg@infradead.org> (raw)
In-Reply-To: <20260918173218.1254465-5-aalbersh@kernel.org>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
prev parent reply other threads:[~2026-09-22 12:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 17:32 [PATCH 0/4] xfstests: random fixes Andrey Albershteyn
2026-09-18 17:32 ` [PATCH 1/4] xfs/071: use _link_out_link instead of opencoding file picking Andrey Albershteyn
2026-09-22 12:37 ` Christoph Hellwig
2026-09-18 17:32 ` [PATCH 2/4] common: link .out file to the output directory Andrey Albershteyn
2026-09-22 12:38 ` Christoph Hellwig
2026-09-22 13:12 ` Andrey Albershteyn
2026-09-18 17:32 ` [PATCH 3/4] generic/452: make coping work with multi-call binary Andrey Albershteyn
2026-09-22 12:40 ` Christoph Hellwig
2026-09-18 17:32 ` [PATCH 4/4] xfstests: fix permissions on system file installed by libtoolize Andrey Albershteyn
2026-09-22 12:40 ` Christoph Hellwig [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=arJ3MNuF_sEs6JUg@infradead.org \
--to=hch@infradead.org \
--cc=aalbersh@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=zlang@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