Date: Thu, 19 Nov 2015 08:28:27 +0100
From: Valentin Rothberg <valentinrothberg@gmail.com>
To: hch@lst.de
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
        Paul Bolle <pebolle@tiscali.nl>, Andreas Ziegler <ziegler@cs.fau.de>,
        schwidefsky@de.ibm.com, airlied@linux.ie
Subject: dma-mappig: HAVE_DMA_ATTR leftovers
Message-ID: <20151119072827.GA1732@debian-vm>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 909
Lines: 24

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/