From: Yogesh Narayan Gaur <yogeshnarayan.gaur@nxp.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mark Brown <broonie@kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Frieder Schrempf <frieder.schrempf@kontron.de>,
Boris Brezillon <bbrezillon@kernel.org>
Subject: RE: linux-next: build warning after merge of the spi tree
Date: Tue, 29 Jan 2019 08:39:55 +0000 [thread overview]
Message-ID: <VI1PR04MB57268573920A23B333CBE68799970@VI1PR04MB5726.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20190129192658.72c88d0b@canb.auug.org.au>
Hi Stephen,
> -----Original Message-----
> From: Stephen Rothwell [mailto:sfr@canb.auug.org.au]
> Sent: Tuesday, January 29, 2019 1:57 PM
> To: Yogesh Narayan Gaur <yogeshnarayan.gaur@nxp.com>
> Cc: Mark Brown <broonie@kernel.org>; Linux Next Mailing List <linux-
> next@vger.kernel.org>; Linux Kernel Mailing List <linux-kernel@vger.kernel.org>;
> Frieder Schrempf <frieder.schrempf@kontron.de>; Boris Brezillon
> <bbrezillon@kernel.org>
> Subject: Re: linux-next: build warning after merge of the spi tree
>
> Hi Yogesh,
>
> On Tue, 29 Jan 2019 06:57:51 +0000 Yogesh Narayan Gaur
> <yogeshnarayan.gaur@nxp.com> wrote:
> >
> > > WARNING: modpost: missing MODULE_LICENSE() in
> > > drivers/spi/spi-nxp-fspi.o see include/linux/module.h for more
> > > information
> > >
> > Can someone help in pointing out that why above warning message is coming
> for mentioned commit.
> > Below MODULE_LICENSE string is present in the above mentioned file,
> drivers/spi/spi-nxp-fspi.c.
> > MODULE_LICENSE("GPL v2");
>
> The version in linux-next has no such line.
>
Yes, somehow this missing line was appended to the commit message instead of the actual in patchwork, also being pointed out by Frieder in his reply.
Sorry for this.
I have send fix patch for this warning message [1]. Please check the patch and apply.
--
Regards,
Yogesh Gaur
[1] https://patchwork.ozlabs.org/patch/1032586/
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2019-01-29 8:39 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 2:02 linux-next: build warning after merge of the spi tree Stephen Rothwell
2019-01-29 6:57 ` Yogesh Narayan Gaur
2019-01-29 7:25 ` Schrempf Frieder
2019-01-29 8:26 ` Stephen Rothwell
2019-01-29 8:39 ` Yogesh Narayan Gaur [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-07 6:31 Stephen Rothwell
2024-05-07 13:16 ` Andy Shevchenko
2024-02-16 3:11 Stephen Rothwell
2024-02-19 11:18 ` Dhruva Gole
2024-02-08 3:52 Stephen Rothwell
2024-02-08 11:43 ` Mark Brown
2024-02-08 13:32 ` Amadeusz Sławiński
2024-02-08 21:59 ` Stephen Rothwell
2022-06-08 4:30 Stephen Rothwell
2022-06-08 7:30 ` David Jander
2022-06-08 10:05 ` Mark Brown
2021-08-10 6:29 Stephen Rothwell
2021-08-09 5:30 Stephen Rothwell
2021-04-20 3:48 Stephen Rothwell
2021-04-20 7:56 ` Patrice CHOTARD
2021-04-06 6:48 Stephen Rothwell
2021-04-06 7:38 ` Jay Fang
2021-01-11 1:09 Stephen Rothwell
2021-01-04 0:06 Stephen Rothwell
2021-01-04 7:56 ` Ardelean, Alexandru
2020-07-09 4:10 Stephen Rothwell
2020-07-09 5:29 ` Peng Fan
2020-04-28 4:16 Stephen Rothwell
2020-04-28 5:01 ` Sanjay R Mehta
2020-04-28 9:38 ` Mark Brown
2020-01-15 2:23 Stephen Rothwell
2020-01-15 9:10 ` Jean Pihet
2020-01-15 10:27 ` Stephen Rothwell
2020-01-15 11:38 ` Jean Pihet
2019-04-29 4:30 Stephen Rothwell
2019-01-10 0:44 Stephen Rothwell
2019-01-10 0:41 Stephen Rothwell
2018-11-14 2:18 Stephen Rothwell
[not found] ` <CAP6Zq1gp+hmNkvk8D2uv8FUqTXE4+ZMPhMB7A7vLMaM6swHy4g@mail.gmail.com>
2018-11-15 19:26 ` Mark Brown
2018-08-03 4:37 Stephen Rothwell
2017-03-27 2:41 Stephen Rothwell
2017-03-27 5:33 ` Vignesh R
2010-10-14 1:59 Stephen Rothwell
2010-10-14 5:00 ` Grant Likely
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=VI1PR04MB57268573920A23B333CBE68799970@VI1PR04MB5726.eurprd04.prod.outlook.com \
--to=yogeshnarayan.gaur@nxp.com \
--cc=bbrezillon@kernel.org \
--cc=broonie@kernel.org \
--cc=frieder.schrempf@kontron.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).