From: Yogesh Narayan Gaur <yogeshnarayan.gaur@nxp•com>
To: "linux-mtd@lists•infradead.org" <linux-mtd@lists•infradead.org>,
"bbrezillon@kernel•org" <bbrezillon@kernel•org>,
"marek.vasut@gmail•com" <marek.vasut@gmail•com>,
"broonie@kernel•org" <broonie@kernel•org>,
"linux-spi@vger•kernel.org" <linux-spi@vger•kernel.org>
Cc: "linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
"linux-next@vger•kernel.org" <linux-next@vger•kernel.org>,
"sfr@canb•auug.org.au" <sfr@canb•auug.org.au>,
"computersforpeace@gmail•com" <computersforpeace@gmail•com>,
"frieder.schrempf@kontron•de" <frieder.schrempf@kontron•de>,
Yogesh Narayan Gaur <yogeshnarayan.gaur@nxp•com>
Subject: [PATCH] spi: spi-mem: spi-nxp-fspi: add module license info
Date: Tue, 29 Jan 2019 08:31:19 +0000 [thread overview]
Message-ID: <1548750550-23565-1-git-send-email-yogeshnarayan.gaur@nxp.com> (raw)
Add MODULE_LICENSE info to fix below warning:
WARNING: modpost: missing MODULE_LICENSE() in drivers/spi/spi-nxp-fspi.o
Signed-off-by: Yogesh Narayan Gaur <yogeshnarayan.gaur@nxp•com>
---
drivers/spi/spi-nxp-fspi.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/spi/spi-nxp-fspi.c b/drivers/spi/spi-nxp-fspi.c
index 0327216ef7aa..90f3d2e4fe5d 100644
--- a/drivers/spi/spi-nxp-fspi.c
+++ b/drivers/spi/spi-nxp-fspi.c
@@ -1103,3 +1103,4 @@ MODULE_AUTHOR("NXP Semiconductor");
MODULE_AUTHOR("Yogesh Narayan Gaur <yogeshnarayan.gaur@nxp•com>");
MODULE_AUTHOR("Boris Brezillion <bbrezillon@kernel•org>");
MODULE_AUTHOR("Frieder Schrempf <frieder.schrempf@kontron•de>");
+MODULE_LICENSE("GPL v2");
--
2.17.1
next reply other threads:[~2019-01-29 8:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 8:31 Yogesh Narayan Gaur [this message]
2019-01-29 8:45 ` [PATCH] spi: spi-mem: spi-nxp-fspi: add module license info Schrempf Frieder
2019-01-29 9:41 ` Boris Brezillon
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=1548750550-23565-1-git-send-email-yogeshnarayan.gaur@nxp.com \
--to=yogeshnarayan.gaur@nxp$(echo .)com \
--cc=bbrezillon@kernel$(echo .)org \
--cc=broonie@kernel$(echo .)org \
--cc=computersforpeace@gmail$(echo .)com \
--cc=frieder.schrempf@kontron$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mtd@lists$(echo .)infradead.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-spi@vger$(echo .)kernel.org \
--cc=marek.vasut@gmail$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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