Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753751AbbFIIPd (ORCPT ); Tue, 9 Jun 2015 04:15:33 -0400 Received: from lb3-smtp-cloud6.xs4all.net ([194.109.24.31]:45485 "EHLO lb3-smtp-cloud6.xs4all.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752228AbbFIIPZ (ORCPT ); Tue, 9 Jun 2015 04:15:25 -0400 Message-ID: <1433837720.16887.42.camel@x220> Subject: Re: [PATCH v4 2/2] dma: Add Xilinx AXI Central Direct Memory Access Engine driver support From: Paul Bolle To: monstr@monstr.eu Cc: Julia Lawall , Kedareswara rao Appana , dan.j.williams@intel.com, vinod.koul@intel.com, michal.simek@xilinx.com, soren.brinkmann@xilinx.com, appanad@xilinx.com, punnaia@xilinx.com, dmaengine@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Srikanth Thokala , Greg Kroah-Hartman , Joe Perches , Fengguang Wu Date: Tue, 09 Jun 2015 10:15:20 +0200 In-Reply-To: <55769132.6070601@monstr.eu> References: <1432228035-6569-1-git-send-email-appanad@xilinx.com> <1432290653.27695.97.camel@x220> <557681A7.7080202@monstr.eu> <55769132.6070601@monstr.eu> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4 (3.10.4-4.fc20) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2177 Lines: 49 On Tue, 2015-06-09 at 09:09 +0200, Michal Simek wrote: > On 06/09/2015 08:10 AM, Julia Lawall wrote: > > On Tue, 9 Jun 2015, Michal Simek wrote: > >> Also sort of checking for this will be great. Julia? > > > > If this requires checking the contents of comment, Coccinelle currently > > can't help with that. Perhaps an idea would be to just do a grep on the > > file. So if I find MODULE_LICENSE("GPL v2") and then grepping for "either > > vresion 2" gives success, then there is a problem? It's obviously not > > foolproof, but perhaps it could be helpful. > > Having some sort of checking somewhere will be great. checkpatch? > zero-day testing system? Mistakes I've seen made since I started checking this stuff (a few months ago): - typos in the license ident, say "GPLv2", "GPL V2", or "BSD": generates a warning when module is loaded and taints kernel. People still get this wrong. A test in checkpatch for these typos was submitted a while ago, but it never got added; - not adding MODULE_LICENSE() to a module: also generates a warning when module is loaded and taints kernel. People still get this wrong; - adding MODULE_LICENSE() to built-in only code: pointless at best, and annoying for reviewers ("Hey, did the submitter intend to write built-in only code or modular code?"); - using "Dual BSD/GPL" but not a trace of the BSD license blurb in sight, while adding that blurb is one of the very few requirements this license actually has; - license mismatch, say comment blurb states "GPL v2 (or later)" but MODULE_LICENSE() ident states "GPL v2" only (or vice versa): very easy mistake to make, happens once or twice a week. Did I miss anything in that list? I'm afraid that most of the above can only be caught reliably by attention to detail by submitters and reviewers. That's a pity, because checking for that stuff is about as boring as it gets. (What does that say about me?) Thanks, Paul Bolle -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/