Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751687AbcCTXnC (ORCPT ); Sun, 20 Mar 2016 19:43:02 -0400 Received: from mail-yw0-f193.google.com ([209.85.161.193]:34870 "EHLO mail-yw0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751118AbcCTXm7 (ORCPT ); Sun, 20 Mar 2016 19:42:59 -0400 From: Joshua Clayton To: Parth Sane Cc: Roger H Newell , Greg KH , "open list:STAGING SUBSYSTEM" , florian.c.schilhabel@googlemail.com, punitvara@gmail.com, bhaktipriya96@gmail.com, linux-kernel@vger.kernel.org, luisbg@osg.samsung.com, Larry.Finger@lwfinger.net Subject: Re: [PATCH 0/5] staging: rtl8712: Fixed Multiple FSF address checkpatch warnings Date: Sun, 20 Mar 2016 16:42:54 -0700 Message-ID: <2297784.63e3uObzUO@diplodocus> User-Agent: KMail/4.14.10 (Linux/4.5.0-gentoo; KDE/4.14.17; x86_64; ; ) In-Reply-To: <41F9AD95-9440-4606-B78B-A74CA684AA9F@gmail.com> References: <41F9AD95-9440-4606-B78B-A74CA684AA9F@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1310 Lines: 29 On Sunday, March 20, 2016 11:12:32 PM Parth Sane wrote: > > Fixed Multiple FSF address checkpatch warnings to conform to kernel coding style. > > > > Parth Sane (5): > > staging: rtl8712: Fixed FSF address warning in basic_types.h > > staging: rtl8712: Fixed FSF address warning in drv_types.h > > staging: rtl9712: Fixed FSF address warning in ethernet.h > > staging: rtl9712: Fixed FSF address warning in hal_init.c > > staging: rtl9712: Fixed FSF address warning in ieee80211.c > > > > drivers/staging/rtl8712/basic_types.h | 4 ---- > > drivers/staging/rtl8712/drv_types.h | 4 ---- > > drivers/staging/rtl8712/ethernet.h | 4 ---- > > drivers/staging/rtl8712/hal_init.c | 4 ---- > > drivers/staging/rtl8712/ieee80211.c | 4 ---- > > 5 files changed, 20 deletions(-) > > > > -- > > 1.9.1 > Hi, > The thing is all these patches are related and have a cover letter explaining changes. But this seems to be a trivial change which is self explanatory. > This should possibly suffice. What do you think? > Regards, > Parth Sane The cover letter does not end up in the repository. A cover letter can be helpful, but is not required. You MUST, however add a descriptive commit message to each patch for them to be accepted into the kernel. See Documentation/SubmittingPatches in the kernel sources.