Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754014AbdLFHz5 (ORCPT ); Wed, 6 Dec 2017 02:55:57 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:57214 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753798AbdLFHz5 (ORCPT ); Wed, 6 Dec 2017 02:55:57 -0500 Date: Wed, 6 Dec 2017 08:56:04 +0100 From: "'Greg KH'" To: Dhaval Rajeshbhai Shah Cc: "arnd@arndb.de" , "linux-kernel@vger.kernel.org" , "michal.simek@xilinx.com" , Hyun Kwon Subject: Re: [PATCH] [linux][master][v1] misc: Add Xilinx ZYNQMP VCU logicoreIP init driver Message-ID: <20171206075604.GA920@kroah.com> References: <1512474212-12803-1-git-send-email-dshah@xilinx.com> <20171205133002.GB13746@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1339 Lines: 37 On Wed, Dec 06, 2017 at 06:01:37AM +0000, Dhaval Rajeshbhai Shah wrote: > Hi Greg k-h, > > Thanks a lot for the review. > > Replies inline. As they should be, perhaps you need a better email client :) > > > +config XILINX_VCU > > + tristate "Xilinx VCU Init" > > + default n > > That's always the default, no need for this. > [Dhaval ] : I will remove that. This style of replying is very odd, please use the normal format in the future. > > + help > > + Driver for the Xilinx VCU Init based on the logicoreIP. > > You need a lot more help text here to explain what this driver is, what it is for, and who would need it. > [Dhaval ] : I will provide more help text to provide more help on driver. > > Also, why is this a misc driver? > [Dhaval ] : this driver is for the logicoreIP which is created to support the Processing system and Programmable logic isolation and to provide the clock related information. So this is not a VCU driver and but just a intermediate driver which supports logicoreIP. That's why no subsystem for this. 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. thanks, greg k-h