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]
Date:   Wed, 6 Dec 2017 10:15:53 +0100
From:   'Greg KH' <>
To:     Dhaval Rajeshbhai Shah <>
Cc:     "" <>,
        "" <>,
        "" <>,
        Hyun Kwon <>
Subject: Re: [PATCH] [linux][master][v1] misc: Add Xilinx ZYNQMP VCU
 logicoreIP init driver

On Wed, Dec 06, 2017 at 09:05:51AM +0000, Dhaval Rajeshbhai Shah wrote:
> > Then you need to explain this a lot better, posting a random driver for
> > submission that is expected to be used by another one isn't ok.
> > Post the whole patch series please, we do not add infrastructure to the
> > kernel that is not used right then.
> Can I remove the export api and header file and make this driver generic for the logicoreIP? No other driver will depend on that. This will help us to remove the isolation between the Programmable system and Programmable logic by configuring the logicoreIp register set.

I don't know, let's see what that patch submission looks like.  If it
doesn't do anything, that's not really a good idea :)

What's wrong with just submitting your entire driver series?  Why break
it up like this?  That's normally not a good idea, you want us to review
it in a "whole" idea, not piece-meal.


greg k-h

Powered by blists - more mailing lists