public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ramuthevar, Vadivel MuruganX"  <vadivel.muruganx.ramuthevar@linux.intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Kishon Vijay Abraham I <kishon@ti.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andy Shevchenko <andriy.shevchenko@intel.com>
Subject: Re: linux-next: build warning after merge of the phy-next tree
Date: Tue, 7 Jan 2020 13:26:39 +0800	[thread overview]
Message-ID: <e09d6254-4ff6-93b4-f007-e256db135e47@linux.intel.com> (raw)
In-Reply-To: <20200107161733.3c70149b@canb.auug.org.au>

Hi,

On 7/1/2020 1:17 PM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the phy-next tree, today's linux-next build (86_64
> allmodconfig) produced this warning:
>
> WARNING: modpost: missing MODULE_LICENSE() in drivers/phy/intel/phy-intel-emmc.o
> see include/linux/module.h for more information
>
> Introduced by commit
>
>    95f1061f715e ("phy: intel-lgm-emmc: Add support for eMMC PHY")

sorry,  will fix it and update.

Thanks!

---
Regards
Vadivel

  reply	other threads:[~2020-01-07  5:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-07  5:17 linux-next: build warning after merge of the phy-next tree Stephen Rothwell
2020-01-07  5:26 ` Ramuthevar, Vadivel MuruganX [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-03-28  0:29 Stephen Rothwell
2019-03-28  3:03 ` Srinath Mannam
2017-08-22  5:07 Stephen Rothwell
2017-08-24  5:23 ` Stephen Rothwell
2017-08-24  8:01   ` Kishon Vijay Abraham I
2016-11-16  3:00 Stephen Rothwell
2016-11-16 13:28 ` wlf
2016-11-16 16:39   ` Kishon Vijay Abraham I

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=e09d6254-4ff6-93b4-f007-e256db135e47@linux.intel.com \
    --to=vadivel.muruganx.ramuthevar@linux.intel.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=kishon@ti.com \
    --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