From: Pankaj Raghav <pankaj.raghav@linux.dev>
To: Carlos Maiolino <cem@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Pankaj Raghav <p.raghav@samsung.com>,
linux-xfs@vger.kernel.org, bfoster@redhat.com,
dchinner@redhat.com, "Darrick J . Wong" <djwong@kernel.org>,
gost.dev@samsung.com, andres@anarazel.de, lukas@herbolt.com
Subject: Re: [RFC 1/2] xfs: add flags field to xfs_alloc_file_space
Date: Wed, 4 Mar 2026 10:46:53 +0100 [thread overview]
Message-ID: <ecd24894-bd95-40d1-9f3f-579a6b666391@linux.dev> (raw)
In-Reply-To: <aaf6QgbmQQ56ZlhH@nidhogg.toxiclabs.cc>
On 3/4/2026 10:31 AM, Carlos Maiolino wrote:
>>>> @@ -646,7 +646,8 @@ int
>>>> xfs_alloc_file_space(
>>>> struct xfs_inode *ip,
>>>> xfs_off_t offset,
>>>> - xfs_off_t len)
>>>> + xfs_off_t len,
>>>> + uint32_t flags)
>>>
>>> Messed up indentation.
>>>
>> Oops.
>>
>>> Given that we've been through this for a lot of iterations, what
>>> about you just take Lukas' existing patch and help improving it?
>>
>> I did review his patch[1]. The patches were broken when I tested it but I
>> did not get a reply from him after I reported them. That is why I decided
>> to send a new version.
>>
>> [1] https://lore.kernel.org/linux-xfs/wmxdwtvahubdga73cgzprqtj7fxyjgx5kxvr4cobtl6ski2i6y@ic2g3bfymkwi/
>
> If I properly got the timeline, you barely gave him time to reply:
>
> your reply to the original patch: Date: Thu, 26 Feb 2026 14:44:05 +0000
> your RFC time: Date: Fri, 27 Feb 2026 15:08:40 +0100
>
> You are around enough time to know that people usually requires more
> than 24 hours to reply.
>
I started working on this in parallel before I realized it was already being
worked on. I could have waited a bit longer after responding to his patches. :)
. Sorry for that.
> Please, work with him to get this done. It's not a nice thing to do IMHO
> to pass over somebody's else work if you are aware there is work being
> done.
>
> FWIW you also didn't Cc'ed him in your RFC as you used the wrong email
> address... I'm fixing the headers so he gets aware of it.
>
Yes, I replied back to the thread with the correct ID [1].
> If by any means I got the timeline wrong above, forget everything I said
> other than the "work with him to get this done".
>
His patches are not working properly. It is almost a week since I sent that
message on his thread. I have messaged him again on how to proceed. I will wait
and see what he replies :)
[1]
https://lore.kernel.org/linux-xfs/20260227140842.1437710-1-p.raghav@samsung.com/T/#mb773dea20a7fc37772f811b26a5c5dd8941c3d2d
--
Pankaj
next prev parent reply other threads:[~2026-03-04 9:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 14:08 [RFC 0/2] add FALLOC_FL_WRITE_ZEROES support to xfs Pankaj Raghav
2026-02-27 14:08 ` [RFC 1/2] xfs: add flags field to xfs_alloc_file_space Pankaj Raghav
2026-03-03 15:24 ` Christoph Hellwig
2026-03-04 8:20 ` Pankaj Raghav (Samsung)
2026-03-04 8:31 ` Pankaj Raghav (Samsung)
2026-03-04 9:31 ` Carlos Maiolino
2026-03-04 9:46 ` Pankaj Raghav [this message]
2026-03-04 14:39 ` Lukas Herbolt
2026-03-04 19:57 ` Pankaj Raghav (Samsung)
2026-02-27 14:08 ` [RFC 2/2] xfs: add support for FALLOC_FL_WRITE_ZEROES Pankaj Raghav
2026-02-27 16:26 ` [RFC 0/2] add FALLOC_FL_WRITE_ZEROES support to xfs Pankaj Raghav (Samsung)
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=ecd24894-bd95-40d1-9f3f-579a6b666391@linux.dev \
--to=pankaj.raghav@linux.dev \
--cc=andres@anarazel.de \
--cc=bfoster@redhat.com \
--cc=cem@kernel.org \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=gost.dev@samsung.com \
--cc=hch@infradead.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lukas@herbolt.com \
--cc=p.raghav@samsung.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