Re: [pull-request] NFC updates for next-next 2026-08-17

[David Heidelberg <david@ixit.cz>]

On 17/08/2026 20:53, Jakub Kicinski wrote:
> On Mon, 17 Aug 2026 19:45:45 +0200 David Heidelberg wrote:
>> The following changes since commit 8d3ae59288f1e7d58d76558a6ee96d533bc5019f:
>>
>>     Linux 7.2 (2026-08-16 14:32:26 -0700)
>>
>> are available in the Git repository at:
>>
>>     https://codeberg.org/linux-nfc/linux.git tags/nfc-net-next-20260817
> 
> Please don't rebase your trees. The base of your tree should be at
> whatever point net-next was after the previous PR to net-next.
> Because:
>   - we don't have the 7.2 tag in our trees yet, if I merge this it will
>     look like I pulled a week worth of Linus's tree, not a small PR from
>     you
>   - the commit hashes in linux-next do not match what you have in this PR

Found reflog of the rc7, thus [1] should be identical.

[1] https://lore.kernel.org/netdev/7fc49075-884e-4284-b742-7057cbba4b17@ixit.cz/>
> Did you rebase this tree recently? Perhaps you still have the previous
> version in git reflog that we could pull instead? Exceptionally, this
> time you may need to rebase to go back to an older base..
> 
> BTW normally to get your own fixes into your own -next tree you should
> stagger the PRs - first send the fixes, after net -> net-next merge on
> Thu afternoon - send the -next PR.

Sure, I'll keep that on my mind. In this case both fixes and next shouldn't 
conflict, thus order in which this gets applied shouldn't matter.

Thank you
David

>