linux-kernel - dma-mappig: HAVE_DMA

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]

Date:	Thu, 19 Nov 2015 08:28:27 +0100
From:	Valentin Rothberg <valentinrothberg@...il.com>
To:	hch@....de
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	Paul Bolle <pebolle@...cali.nl>,
	Andreas Ziegler <ziegler@...fau.de>, schwidefsky@...ibm.com,
	airlied@...ux.ie
Subject: dma-mappig: HAVE_DMA_ATTR leftovers

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/