From: "Ferry Toth" <fntoth@gmail.com>
To: Mark Hatle <mark.hatle@kernel.crashing.org>,
yocto-patches@lists.yoctoproject.org,
Gyorgy Sarvari <skandigraun@gmail.com>
Subject: Re: [yocto-patches] [pseudo][PATCH v2 2/2] nftw, ftw: add tests
Date: Sat, 26 Apr 2025 23:14:19 +0200 [thread overview]
Message-ID: <727bd608-5ccd-4a2a-901e-2f86389c7d68@gmail.com> (raw)
In-Reply-To: <1bd5bd95-8387-4f76-8018-389738f3f910@kernel.crashing.org>
Hi Mark,
Op 08-04-2025 om 18:06 schreef Mark Hatle:
>
>
> On 4/8/25 9:33 AM, Gyorgy Sarvari via lists.yoctoproject.org wrote:
>> On 4/7/25 21:14, Gyorgy Sarvari via lists.yoctoproject.org wrote:
>>> +#if !defined(__USE_LARGEFILE64) && FTW_NAME == ftw64
>>> +return 0
>>> +#endif
>> If nothing else, at the very least a semicolon is missing in this short
>> path when the call is not available (and in its nftw64 pair). Will keep
>> it in mind to fix - won't submit a v3 only with this on my own.
>
> Thanks, I'll add this to my local merge for review and testing.
Tested-by: Ferry Toth <fntoth@gmail.com>
This is an import patch for walnascar and master. The reason is that
walnascar already (even though it is not released) has btrfs-tools 6.13
which will not generate bootable images without this patch.
Also, scarthgap has btrfs-tools 6.7.1 which creates an image with errors
(2000 in my case, or maybe it stops counting). Luckily that image boots.
But scarthgap being LTS imho should have a backported btrfs-tools and
because of that also pseudo with this patch or similar.
I tested this on Intel Edison scarthgap with this patch in a bbappend
(and the other pseudo patches refreshed and git formatted).
> --Mark
>
>>
>>
>>
>
next prev parent reply other threads:[~2025-04-28 8:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 19:14 [pseudo][PATCH v2 0/2] nftw, ftw: add wrappers Gyorgy Sarvari
2025-04-07 19:14 ` [pseudo][PATCH v2 1/2] nftw, ftw: add wrapper Gyorgy Sarvari
2025-04-07 19:14 ` [pseudo][PATCH v2 2/2] nftw, ftw: add tests Gyorgy Sarvari
2025-04-07 23:11 ` [yocto-patches] [pseudo][PATCH v2 0/2] nftw, ftw: add wrappers Mark Hatle
[not found] ` <18341F33308F8E0B.31078@lists.yoctoproject.org>
2025-04-08 14:33 ` [yocto-patches] [pseudo][PATCH v2 2/2] nftw, ftw: add tests Gyorgy Sarvari
2025-04-08 16:06 ` Mark Hatle
2025-04-26 21:14 ` Ferry Toth [this message]
[not found] ` <18342C3498EB800F.31078@lists.yoctoproject.org>
2025-05-02 1:08 ` [yocto-patches] [pseudo][PATCH v2 0/2] nftw, ftw: add wrappers Mark Hatle
2025-05-02 1:17 ` Mark Hatle
2025-05-02 8:53 ` Gyorgy Sarvari
2025-05-02 13:33 ` Mark Hatle
[not found] ` <183BA9D5657FA6B7.6015@lists.yoctoproject.org>
2025-05-02 9:53 ` Gyorgy Sarvari
2025-05-02 13:42 ` Mark Hatle
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=727bd608-5ccd-4a2a-901e-2f86389c7d68@gmail.com \
--to=fntoth@gmail.com \
--cc=mark.hatle@kernel.crashing.org \
--cc=skandigraun@gmail.com \
--cc=yocto-patches@lists.yoctoproject.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.