linux-kernel - Re: [PATCHv3 00/16] vme DMA and user space driver improvements

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150613022455.GA3315@kroah.com>
Date:	Fri, 12 Jun 2015 19:24:55 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Dmitry Kalinkin <dmitry.kalinkin@...il.com>
Cc:	devel@...verdev.osuosl.org, Martyn Welch <martyn.welch@...com>,
	Manohar Vanga <manohar.vanga@...il.com>,
	Igor Alekseev <igor.alekseev@...p.ru>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCHv3 00/16] vme DMA and user space driver improvements

On Sat, Jun 13, 2015 at 05:04:28AM +0300, Dmitry Kalinkin wrote:
> On Sat, Jun 13, 2015 at 3:31 AM, Greg Kroah-Hartman
> <gregkh@...uxfoundation.org> wrote:
> > On Wed, Jun 10, 2015 at 04:09:19PM +0300, Dmitry Kalinkin wrote:
> >> Also, there are some patches that IMO don't need any special VME
> >> subsystem expertise, namely:
> >>   Documentation: mention vme_master_mmap() in VME API
> >>   vme: ca91cx42: return error code on DMA error
> >>   staging: vme_user: remove unused counters
> >>   staging: vme_user: remove forward declarations
> >>   staging: vme_user: remove open/release
> >>   staging: vme_user: remove buf_unalloc helper
> >>   vme: tsi148: depend on HAS_DMA for Kconfig
> >
> > I've taken all of these except patches 12, 13, 14 and 16.
> >
> I thought 12 was the most harmless out of the whole set. Am I wrong?

You added a new userspace api, that someone else is going to have to
maintain, that's not "harmless" at all.
--
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/