Re: [GIT PULL] ntfs updates for 7.1-rc1
From: Namjae Jeon
Date: Thu Apr 16 2026 - 23:26:54 EST
On Fri, Apr 17, 2026 at 11:52 AM Linus Torvalds
<torvalds@xxxxxxxxxxxxxxxxxxxx> wrote:
>
> On Thu, 16 Apr 2026 at 08:05, Namjae Jeon <linkinjeon@xxxxxxxxxx> wrote:
> >
> > This series has been in linux-next for approximately two months. During
> > that time, additional fixes from Smatch static analysis and the patches
> > from other developers have been incorporated, including two build fixes
> > from Mark Brown(VMA descriptor rename and inode lookup u64 change) that
> > were picked up from linux-next.
>
> I pulled this for testing, but this is not at all how any of this can work.
>
> The branch I pulled does NOT EVEN BUILD.
>
> It has been updated for new semantics that do not exist in that
> branch, and that's not at all how any of this can ever work. If
> anybody ever bisects into that tree, they get a failed build. Not ok.
>
> This is something that I would have done at merge time as a fix for a
> semantic conflict, not something that you can do in your tree that
> makes the source tree not even build any more, and only build once it
> has been merged upstream.
>
> So no. We don't proactively "fix" merge issues by making the source
> tree not work at all.
>
> I have unpulled this.
I apologize for the oversight. I clearly misunderstood the proper way
to handle these semantic conflicts and broke the bisectability of my
own tree. I will rebase the patches on top of the latest upstream,
ensure that each commit builds correctly on its own, and resubmit the
pull request.
Thanks.