From: Parth Sane <laerdevstudios@gmail.com>
To: laerdevstudios@gmail.com, gregkh@linuxfoundation.org
Cc: Larry.Finger@lwfinger.net, florian.c.schilhabel@googlemail.com,
luisbg@osg.samsung.com, bhaktipriya96@gmail.com,
stillcompiling@gmail.com, punitvara@gmail.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/5] staging: rtl8712: Fixed checkpatch warning due to FSF address block
Date: Mon, 21 Mar 2016 08:17:31 +0000 [thread overview]
Message-ID: <cover.1458547090.git.laerdevstudios@gmail.com> (raw)
Fixed checkpatch warning caused due to FSF address block.
Linux already has a copy of the GPL, so as per checkpatch this address block is
unnecessary.
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
next reply other threads:[~2016-03-21 8:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 8:17 Parth Sane [this message]
2016-03-21 8:17 ` [PATCH v2 1/5] staging: rtl8712: Fixed FSF address warning in basic_types.h Parth Sane
2016-03-21 8:17 ` [PATCH v2 2/5] staging: rtl8712: Fixed FSF address warning in drv_types.h Parth Sane
2016-03-21 8:17 ` [PATCH v2 3/5] staging: rtl9712: Fixed FSF address warning in ethernet.h Parth Sane
2016-03-21 21:27 ` Greg KH
2016-03-21 8:17 ` [PATCH v2 4/5] staging: rtl9712: Fixed FSF address warning in hal_init.c Parth Sane
2016-03-21 21:27 ` Greg KH
2016-03-21 8:17 ` [PATCH v2 5/5] staging: rtl9712: Fixed FSF address warning in ieee80211.c Parth Sane
2016-03-21 21:28 ` 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=cover.1458547090.git.laerdevstudios@gmail.com \
--to=laerdevstudios@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=linux-kernel@vger.kernel.org \
--cc=luisbg@osg.samsung.com \
--cc=punitvara@gmail.com \
--cc=stillcompiling@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