Skip to contentSkip to conversation

dma-mappig: HAVE_DMA_ATTR leftovers

DISCUSSION Valentin Rothberg 2 participants 2 messages Nov 19, 2015

lore
Share & tools
lore
#0 lore raw

Hi Christoph,

your commit f6f306eeb7ea ("dma-mapping: always provide the dma_map_ops based implementation") has shown up in today's linux-next tree (i.e., next-20151119). The commit removes the Kconfig option HAVE_DMA_ATTR and does some related clean-ups, but it leaves two references in Kconfig untouched:

arch/s390/Kconfig:129: select HAVE_DMA_ATTRS drivers/gpu/drm/vc4/Kconfig:4: depends on DRM && HAVE_DMA_ATTRS

Is there a patched queued somewhere to fix those leftovers? If not, I can send a trivial patch that removes both.

I found the issue with scripts/checkkconfigsymbols.py by diffing yesterday's and today's linux-next.

Best regards,
Valentin

#1 lore raw

Thanks Valention,

please send the fixup to Andrew. Looks like both instances were actually introduces after I prepared my patches.