From: Florian Fainelli <f.fainelli@gmail.com>
To: Eric Sandeen <sandeen@sandeen.net>,
"Darrick J. Wong" <djwong@kernel.org>
Cc: xfs <linux-xfs@vger.kernel.org>,
Fabrice Fontaine <fontaine.fabrice@gmail.com>
Subject: Re: [RFC PATCH] libxfs: stop overriding MAP_SYNC in publicly exported header files
Date: Mon, 8 Aug 2022 10:13:06 -0700 [thread overview]
Message-ID: <14b36a0e-b567-e854-8791-0aed7af0567a@gmail.com> (raw)
In-Reply-To: <86691238-3de4-418d-5e94-981de043173e@sandeen.net>
On 8/4/22 19:11, Eric Sandeen wrote:
>
>
> On 7/29/22 10:48 AM, Darrick J. Wong wrote:
>>> Darrick, do you need to re-post, or can the maintainers pick up the patch directly?
>> I already did:
>> https://lore.kernel.org/linux-xfs/YtmB005kkkErb5uw@magnolia/
>>
>> (It's August, so I think the xfsprogs maintainer might be on vacation?
>> Either way, I'll make sure he's aware of it before the next release.)
>>
>> --D
>>
>
> Yep I was, picking it up now. Thanks for the pointer Darrick.
>
> -Eric
Eric, any chance this could be pushed to xfsprogs-dev.git so we can take
the patch and submit it to buildroot, OpenWrt and other projects that
depend upon that build fix?
Thanks!
--
Florian
next prev parent reply other threads:[~2022-08-08 17:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <WVSe_1J22WBxe1bXs0u1-LcME14brH0fGDu5RCt5eBvqFJCSvxxAEPHIObGT4iqkEoCCZv4vpOzGZSrLjg8gcQ==@protonmail.internalid>
2022-07-20 23:28 ` [RFC PATCH] libxfs: stop overriding MAP_SYNC in publicly exported header files Darrick J. Wong
2022-07-21 3:29 ` Florian Fainelli
2022-07-21 12:11 ` Carlos Maiolino
2022-07-28 22:29 ` Florian Fainelli
2022-07-29 15:48 ` Darrick J. Wong
2022-08-05 2:11 ` Eric Sandeen
2022-08-08 17:13 ` Florian Fainelli [this message]
2022-08-08 17:36 ` Darrick J. Wong
2022-08-08 17:37 ` Florian Fainelli
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=14b36a0e-b567-e854-8791-0aed7af0567a@gmail.com \
--to=f.fainelli@gmail.com \
--cc=djwong@kernel.org \
--cc=fontaine.fabrice@gmail.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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