linux-kernel - Re: [PATCH 0/5] staging: rtl8712: Fixed Multiple FSF address checkpatch warnings

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2297784.63e3uObzUO@diplodocus>
Date:	Sun, 20 Mar 2016 16:42:54 -0700
From:	Joshua Clayton <stillcompiling@...il.com>
To:	Parth Sane <laerdevstudios@...il.com>
Cc:	Roger H Newell <newell.roger@...il.com>,
	Greg KH <gregkh@...uxfoundation.org>,
	"open list:STAGING SUBSYSTEM" <devel@...verdev.osuosl.org>,
	florian.c.schilhabel@...glemail.com, punitvara@...il.com,
	bhaktipriya96@...il.com, linux-kernel@...r.kernel.org,
	luisbg@....samsung.com, Larry.Finger@...inger.net
Subject: Re: [PATCH 0/5] staging: rtl8712: Fixed Multiple FSF address checkpatch warnings

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.