linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Baolin Wang <baolin.wang7@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Baolin Wang <baolin.wang@linaro.org>,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: linux-next: build warning after merge of the mmc tree
Date: Thu, 20 Feb 2020 09:38:12 +0800	[thread overview]
Message-ID: <CADBw62pLjzq83Gzfr0T7fmxFRevb+m5P4LQuq4dPmgRswOhMoQ@mail.gmail.com> (raw)
In-Reply-To: <20200220103105.01d7c0c1@canb.auug.org.au>

Hi Stephen,

On Thu, Feb 20, 2020 at 7:31 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> After merging the mmc tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
>
> WARNING: modpost: missing MODULE_LICENSE() in drivers/mmc/host/mmc_hsq.o
> see include/linux/module.h for more information

I am sorry I missed this warning before, and I've sent out a patch to
fix this warning[1]. Thanks for reporting.

[1] https://lore.kernel.org/patchwork/patch/1196938/

  reply	other threads:[~2020-02-20  1:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-19 23:31 linux-next: build warning after merge of the mmc tree Stephen Rothwell
2020-02-20  1:38 ` Baolin Wang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-08-25  3:20 Stephen Rothwell
2019-10-22  0:47 Stephen Rothwell
2019-10-22  7:31 ` Ulf Hansson
2019-03-19  1:15 Stephen Rothwell
2017-11-02  1:36 Stephen Rothwell
2017-11-02  1:47 ` Doug Anderson
2017-11-02 15:03   ` Ulf Hansson

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=CADBw62pLjzq83Gzfr0T7fmxFRevb+m5P4LQuq4dPmgRswOhMoQ@mail.gmail.com \
    --to=baolin.wang7@gmail.com \
    --cc=arnd@arndb.de \
    --cc=baolin.wang@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=ulf.hansson@linaro.org \
    /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).