public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joshua Clayton <stillcompiling@gmail.com>
To: Parth Sane <laerdevstudios@gmail.com>
Cc: Roger H Newell <newell.roger@gmail.com>,
	Greg KH <gregkh@linuxfoundation.org>,
	"open list:STAGING SUBSYSTEM" <devel@driverdev.osuosl.org>,
	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	[thread overview]
Message-ID: <2297784.63e3uObzUO@diplodocus> (raw)
In-Reply-To: <41F9AD95-9440-4606-B78B-A74CA684AA9F@gmail.com>

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.

  reply	other threads:[~2016-03-20 23:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-20 15:58 [PATCH 0/5] staging: rtl8712: Fixed Multiple FSF address checkpatch warnings Parth Sane
2016-03-20 15:58 ` [PATCH 1/5] staging: rtl8712: Fixed FSF address warning in basic_types.h Parth Sane
2016-03-21 21:27   ` Greg KH
2016-03-20 15:58 ` [PATCH 2/5] staging: rtl8712: Fixed FSF address warning in drv_types.h Parth Sane
2016-03-20 15:58 ` [PATCH 3/5] staging: rtl9712: Fixed FSF address warning in ethernet.h Parth Sane
2016-03-20 15:59 ` [PATCH 4/5] staging: rtl9712: Fixed FSF address warning in hal_init.c Parth Sane
2016-03-20 15:59 ` [PATCH 5/5] staging: rtl9712: Fixed FSF address warning in ieee80211.c Parth Sane
2016-03-20 17:35 ` [PATCH 0/5] staging: rtl8712: Fixed Multiple FSF address checkpatch warnings Roger H Newell
2016-03-20 17:42   ` Parth Sane
2016-03-20 23:42     ` Joshua Clayton [this message]
2016-03-21 21:27 ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2297784.63e3uObzUO@diplodocus \
    --to=stillcompiling@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=bhaktipriya96@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=florian.c.schilhabel@googlemail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=laerdevstudios@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luisbg@osg.samsung.com \
    --cc=newell.roger@gmail.com \
    --cc=punitvara@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox