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
Date: Thu, 19 Nov 2015 08:28:27 +0100 [thread overview]
Message-ID: <20151119072827.GA1732@debian-vm> (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
next reply other threads:[~2015-11-19 7:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 7:28 Valentin Rothberg [this message]
2015-11-19 7:31 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151119072827.GA1732@debian-vm \
--to=valentinrothberg@gmail.com \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=schwidefsky@de.ibm.com \
--cc=ziegler@cs.fau.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome