From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932669AbcINQbf (ORCPT ); Wed, 14 Sep 2016 12:31:35 -0400 Received: from mail-wm0-f53.google.com ([74.125.82.53]:38809 "EHLO mail-wm0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1761247AbcINQbb (ORCPT ); Wed, 14 Sep 2016 12:31:31 -0400 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 X-Mailer: BlackBerry Email (10.3.2.2876) Message-ID: <20160914163122.6131795.78107.2584@gmail.com> Date: Wed, 14 Sep 2016 19:31:22 +0300 Subject: Re: drivers: staging: vme: Fixed some code style warnings From: Andrew Kanner In-Reply-To: References: <1473719504-14435-1-git-send-email-andrew.kanner@gmail.com> To: =?utf-8?q?Markus_B=C3=B6hme?= , gregkh@linuxfoundation.org Cc: devel@driverdev.osuosl.org, manohar.vanga@gmail.com, egor.ulieiskii@gmail.com, linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id u8EGViW9031978 ‎Thanks, I understood my fault, but haven't done this changes yet. I can't understand if I should reply to original message with v2 patch or send a new email with it?   Исходное сообщение   От: Markus Böhme Отправлено: среда, 14 сентября 2016 г., 15:56 Кому: Andrew Kanner; gregkh@linuxfoundation.org Копия: devel@driverdev.osuosl.org; manohar.vanga@gmail.com; egor.ulieiskii@gmail.com; linux-kernel@vger.kernel.org Тема: Re: drivers: staging: vme: Fixed some code style warnings On 09/13/2016 12:31 AM, Andrew Kanner wrote: > Signed-off-by: Andrew Kanner > --- > drivers/staging/vme/devices/vme_pio2_core.c | 12 ++++++------ > drivers/staging/vme/devices/vme_user.c | 2 +- > 2 files changed, 7 insertions(+), 7 deletions(-) > (snip) Hello Andrew, please be more specific in your subject line, e.g. "drivers: staging: vme: Convert to octal notation for permission bits". Also don't forget to add a commit message to your patch with a short description what you are fixing and why. In your case it would be good to mention that you are fixing a checkpatch warning, and to include the warning message in your description. Then resend as V2. Thanks, Markus