linux-kernel - Re: [PATCH 001/115] gpu: ion: Add ION Memory Manager

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: <20131213235028.GA4919@kroah.com>
Date:	Fri, 13 Dec 2013 15:50:28 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	John Stultz <john.stultz@...aro.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Android Kernel Team <kernel-team@...roid.com>,
	Sumit Semwal <sumit.semwal@...aro.org>,
	Jesse Barker <jesse.barker@....com>,
	Colin Cross <ccross@...roid.com>,
	Rebecca Schultz Zavin <rebecca@...roid.com>
Subject: Re: [PATCH 001/115] gpu: ion: Add ION Memory Manager

On Fri, Dec 13, 2013 at 02:23:35PM -0800, John Stultz wrote:
> From: Rebecca Schultz Zavin <rebecca@...roid.com>
> 
> Signed-off-by: Rebecca Schultz Zavin <rebecca@...roid.com>
> [jstultz: Squished in Colin Cross' move to staging change]
> Signed-off-by: John Stultz <john.stultz@...aro.org>
> ---
>  drivers/staging/android/Kconfig                 |    2 +
>  drivers/staging/android/Makefile                |    2 +

This patch breaks the build if this option is enabled.

I suggest only adding the driver to the build _after_ it can be built,
for obvious reasons :)

Other than this "minor" thing, I have no objection to these patches at
all.  Can you redo this patch to fix this up, and maybe send another
patch adding it to the build and let me know at what point in the series
it should be applied?

Also, I only received 92 of these patches, not all 115, are they stuck
somewhere in a mail queue?

thanks,

greg k-h
--
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/