public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arun Parameswaran <aparames@broadcom.com>
To: kernel test robot <ying.huang@linux.intel.com>,
	Arun Parameswaran <arunp@broadcom.com>
Cc: <lkp@01.org>, LKML <linux-kernel@vger.kernel.org>,
	0day robot <fengguang.wu@intel.com>
Subject: Re: [lkp] [net] 041de4d656: bcm_phy_lib: module license 'unspecified' taints kernel.
Date: Tue, 13 Oct 2015 12:25:06 -0700	[thread overview]
Message-ID: <561D5A92.2030800@broadcom.com> (raw)
In-Reply-To: <87h9lwliey.fsf@yhuang-dev.intel.com>



On 15-10-11 11:17 PM, kernel test robot wrote:
> FYI, we noticed the below changes on
>
> git://internal_mailing_list_patch_tree Arun-Parameswaran/Add-support-for-Broadcom-s-iProc-MDIO-and-Cygnus-Ethernet-PHY
> commit 041de4d6564535f639f0d4cec6712b5adf62723f ("net: phy: Add Broadcom phy library for common interfaces")
>
> Found new message as below in kernel log after the commit.
>
> [    2.527336] bcm_phy_lib: module license 'unspecified' taints kernel.
> [    2.527686] Disabling lock debugging due to kernel taint

Will fix this with a separate patch.

>
> To reproduce:
>
>         git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
>         cd lkp-tests
>         bin/lkp install job.yaml  # job file is attached in this email
>         bin/lkp run     job.yaml
>
>
>
> Thanks,
> Ying Huang

Thanks,

Arun


      reply	other threads:[~2015-10-13 19:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-12  6:17 [lkp] [net] 041de4d656: bcm_phy_lib: module license 'unspecified' taints kernel kernel test robot
2015-10-13 19:25 ` Arun Parameswaran [this message]

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=561D5A92.2030800@broadcom.com \
    --to=aparames@broadcom.com \
    --cc=arunp@broadcom.com \
    --cc=fengguang.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=ying.huang@linux.intel.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