Re: [PATCH 0/3] use vm_flags_t consistently

2025-06-25 Thread Lorenzo Stoakes
On Tue, Jun 24, 2025 at 09:50:50PM -0700, Andrew Morton wrote: > On Wed, 25 Jun 2025 08:25:35 +0530 Anshuman Khandual > wrote: > > > ust wondering which tree-branch this series applies ? Tried all the usual > > ones but could not apply the series cleanly. > > > > v6.16-rc3 > > next-20250624 > > m

Re: [PATCH 0/3] use vm_flags_t consistently

2025-06-24 Thread Andrew Morton
On Wed, 25 Jun 2025 08:25:35 +0530 Anshuman Khandual wrote: > ust wondering which tree-branch this series applies ? Tried all the usual > ones but could not apply the series cleanly. > > v6.16-rc3 > next-20250624 > mm-stable > mm-unstable It's now in mm-unstable if that helps.

Re: [PATCH 0/3] use vm_flags_t consistently

2025-06-24 Thread Anshuman Khandual
On 19/06/25 1:12 AM, Lorenzo Stoakes wrote: > The VMA flags field vma->vm_flags is of type vm_flags_t. Right now this is > exactly equivalent to unsigned long, but it should not be assumed to be. > > Much code that references vma->vm_flags already correctly uses vm_flags_t, > but a fairly large ch

Re: [PATCH 0/3] use vm_flags_t consistently

2025-06-18 Thread Mike Rapoport
On Wed, Jun 18, 2025 at 08:42:51PM +0100, Lorenzo Stoakes wrote: > The VMA flags field vma->vm_flags is of type vm_flags_t. Right now this is > exactly equivalent to unsigned long, but it should not be assumed to be. > > Much code that references vma->vm_flags already correctly uses vm_flags_t, >