From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753402Ab0IOF47 (ORCPT ); Wed, 15 Sep 2010 01:56:59 -0400 Received: from mail-iw0-f174.google.com ([209.85.214.174]:37832 "EHLO mail-iw0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750774Ab0IOF46 (ORCPT ); Wed, 15 Sep 2010 01:56:58 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=Ug/SRIXQ6EUvDSNDNDW4v0olGiFXG3NbUM856SKvfyNnHBw3EgrVuRYdX4CpjVlo6e ZRd4/tbCYlj+aZv19kgwd7aIIUa/vseiCFdRCP9+617lgAe/205sZI8bqxwvmu9dy0Ui 6epOzp+dTSb94u4RNX4B5JLHBJvuRg4oDK2h8= Date: Tue, 14 Sep 2010 22:56:49 -0700 From: Dmitry Torokhov To: Vladislav Bolkhovitin Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org, scst-devel , James Bottomley , Andrew Morton , FUJITA Tomonori , Mike Christie , Jeff Garzik , Vu Pham , Bart Van Assche , James Smart , Joe Eykholt , Andy Yan , Chetan Loke , Hannes Reinecke , Richard Sharpe Subject: Re: [PATCH 0/17]: New SCSI target framework (SCST) with dev handlers and 2 target drivers Message-ID: <20100915055649.GB22219@core.coreip.homeip.net> References: <4C8F886E.2080407@vlnb.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C8F886E.2080407@vlnb.net> User-Agent: Mutt/1.5.20 (2009-12-10) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Vladislav, On Tue, Sep 14, 2010 at 06:36:30PM +0400, Vladislav Bolkhovitin wrote: > Hi All, > > Please review this second iteration of the patch set of the new > (although, perhaps, the oldest) SCSI target framework for Linux SCST > with a set of dev handlers and 2 target drivers: for local access > (scst_local) and for Infiniband SRP (srpt). > I am afraid that the way the code was split into the patches will hinder the review process. Normally every patch consists of a usable on its own piece of code (or a logically compete change). This way the unit of work (coding, testing or reviewing) is clearly defined and easier to comprehend. Your patch series, unfortunately, splits Makefile and Kconfig changes separately from the drivers (which will cause build breakages should it be applied as is and someone needs to bisect), introduces header files in their entirety even when some of the data there is not needed till much later, uses facilities (for example sysfs bindings) that have not been introduced yet... I am afraid you'd have to rework the splitting process. Also patch descriptions should be improved: "This patch contains SYSFS interface implementation" - what are you trying to solve? - main points? - why offloading of actions to a separate thread? This should be in the patch description. BTW, why are you using an exclusive thread instead of exclusive workqueue for this? Also, kobject_del() + kobject_put() == kobject_unregister(). And too many "naked returns", I believe common style is to only have return for non-void functions. Thanks. -- Dmitry