On Fri, 16 Oct 2026 16:48:30 +0000 Hemant Agrawal <[email protected]> wrote:
> Hi Stephan, > > > -----Original Message----- > > From: Stephen Hemminger <[email protected]> > > > > NXP Confidential > > On Fri, 16 Oct 2026 16:49:33 +0530 > > Hemant Agrawal <[email protected]> wrote: > > > > > This series collects a set of fixes and enhancements for the NXP DPAA > > > bus, mempool, dma, crypto and net drivers targeting 26.11. > > > > > > It includes memory-leak and resource-cleanup fixes on the device > > > remove/close paths, more robust frame queue shutdown, > > > secondary-process safety guards, BPID lifecycle handling, and several new > > > > > features: > > > enhanced virtual storage profile (VSP) port support, fmcless Rx queue > > > configuration, non fmX-macY shared Ethernet naming, and DMA > > > scatter-gather and errata-workaround devargs. Documentation and > > > release notes are updated accordingly. > > > > > > V27: > > > - fixed qm_channel_pool_num check issue. > > > - fixed commit message as devarg for fmcless rxq number was removed. > > > - Added missing export internal symbol and fq destroy. > > > - merged both FQ shutdown patches as we cannot change the sequence > > > because of the dependency. > > > - mac_idx has a user which is dpaa flow so no change. Added static to > > > g_fmc_model and updated release notes. > > > - Issues reported in v25 which are not handled, were optional, so > > > skipping them. > > > > > > FYI - what I do is feed the patch into a Claude project with existing > > AGENTS.md > > file. The chat continues as versions get sent to email so the context window > > has all the versions of the patch. This lets it see the progress and check > > if > > previous findings were addressed. > > > > Review of [PATCH v27 00/25] NXP DPAA fixes and enhancements > > > > Series applies cleanly to 26.11-rc1 and every commit builds with - > > Dwerror=true. The fixes are now first. 08 cherry-picks cleanly onto > > v24.11 and v25.11, and 06 applies there once 01-05 are in. > > > > v26 Warnings on 12 (now 14) and 20 are addressed. The 24 Warning is only > > partly fixed. > > > > I see only one warning in this patchset 24/25 - is it possible that you > drop this patch and apply rest of the series? I could if that is what you want
