linux-kernel - Question about ntfs3 git pull request

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <89481e37-6723-6dd5-3549-85d1aa9fccbe@paragon-software.com>
Date:   Fri, 24 Sep 2021 19:47:09 +0300
From:   Konstantin Komarov <almaz.alexandrovich@...agon-software.com>
To:     <sfr@...b.auug.org.au>, <torvalds@...ux-foundation.org>
CC:     <linux-kernel@...r.kernel.org>
Subject: Question about ntfs3 git pull request

Hello, Stephen, Linus!

I have a question about next git pull request.

After first ntfs3 pull request [1] was accepted
there are some new commits, that I want to send for rc5 probably
(need more tests + some time in linux-next).

I've noticed, that I missed step
"If your upstream-bound branch has emptied entirely into the mainline
during the merge window, you can pull it forward with a command like"
from Kernel Maintainer Handbook [2].

Right now my github repo still based on 5.14-rc7.
Do I need to update it with git merge up to 5.15-rcX?
Or will it be ok to send git pull request as is and
back merge master only when 5.15 will release?

[1]: https://lore.kernel.org/linux-fsdevel/aa4aa155-b9b2-9099-b7a2-349d8d9d8fbd@paragon-software.com/T/#u
[2]: https://www.kernel.org/doc/html/latest/maintainer/rebasing-and-merging.html#finally