From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2998408AbdDZKiJ (ORCPT ); Wed, 26 Apr 2017 06:38:09 -0400 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:52011 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2998394AbdDZKiB (ORCPT ); Wed, 26 Apr 2017 06:38:01 -0400 X-ME-Sender: X-Sasl-enc: CgERgDxXB3c/pqyTNgz7tqQyr1LUbdbfTYRw1lyjnHkI 1493203079 Date: Wed, 26 Apr 2017 20:37:56 +1000 From: "Tobin C. Harding" To: Ilia Sergachev Cc: Greg Kroah-Hartman , devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] Staging: ks7010: style fix Message-ID: <20170426103756.GF18468@eros> References: <20170425205925.20439-1-ilia.sergachev@unibas.ch> <20170426083854.18813-1-ilia.sergachev@unibas.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170426083854.18813-1-ilia.sergachev@unibas.ch> X-Mailer: Mutt 1.5.24 (2015-08-30) User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Apr 26, 2017 at 10:38:54AM +0200, Ilia Sergachev wrote: > Fix the style of block comments. > Move trailing */ to a separate line. > Checkpatch was showing: > WARNING: Block comments use a trailing */ on a separate line. You are doing well Ilia. A few nitpicks - Your first subject was better (excluding the filname) :) it was more descriptive. - staging has a small 's'. You can verify with; $ git log --pretty=oneline drivers/staging/ks7010/ks_wlan_net.c - You may like to describe the problem first, then what the patch does to fix it; Documentation/process/submitting-patches.rst Describe your problem. Whether your patch is a one-line bug fix or 5000 lines of a new feature, there must be an underlying problem that motivated you to do this work. Convince the reviewer that there is a problem worth fixing and that it makes sense for them to read past the first paragraph. ... Once the problem is established, describe what you are actually doing about it in technical detail. It's important to describe the change in plain English for the reviewer to verify that the code is behaving as you intend it to. The actual patch looks good to me. Hope this helps, Tobin.