From: Arun Parameswaran <aparames@broadcom.com>
To: David Miller <davem@davemloft.net>,
Arun Parameswaran <arunp@broadcom.com>
Cc: "f.fainelli@gmail.com" <f.fainelli@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>
Subject: Re: [PATCH 1/1] net: phy: bcm-phy-lib: Fix module license issue
Date: Thu, 15 Oct 2015 10:11:07 -0700 [thread overview]
Message-ID: <561FDE2B.7090205@broadcom.com> (raw)
In-Reply-To: <20151014.183947.1675991536904094202.davem@davemloft.net>
On 15-10-14 06:39 PM, David Miller wrote:
> From: Arun Parameswaran <arunp@broadcom.com>
> Date: Tue, 13 Oct 2015 13:40:12 -0700
>
>> The 'bcm-phy-lib.c', added as a part of the commit
>> "net: phy: Add Broadcom phy library for common interfaces"
>> was missing the module license. This was causing an issue
>> when the library is built as a module; "module license
>> 'unspecified' taints kernel".
>>
>> This patch fixes the issue by adding the module license,
>> author and description to the bcm-phy-lib.c file.
>>
>> Fixes: a1cba5613edf5 ("net: phy: Add Broadcom phy library for common
>> interfaces")
>> Signed-off-by: Arun Parameswaran <arunp@broadcom.com>
> This patch doesn't apply to my net-next tree at all.
There is a mismatch in the 'git diff' output, for the last 3 lines in
bcm-phy-lib.c
For some reason the patch I created has '@@ -207,3 +208,6 @@', instead of
'@@ -206,3 +207,7 @@', when created from the 'net-next'.
I will send out a patch based on the 'net-next'.
Thanks
Arun
prev parent reply other threads:[~2015-10-15 17:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 20:40 [PATCH 0/1] Fix for module license in Broadcom Phy Library Arun Parameswaran
2015-10-13 20:40 ` [PATCH 1/1] net: phy: bcm-phy-lib: Fix module license issue Arun Parameswaran
[not found] ` <1444768812-31476-2-git-send-email-arunp-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2015-10-15 1:39 ` David Miller
2015-10-15 17:11 ` 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=561FDE2B.7090205@broadcom.com \
--to=aparames@broadcom.com \
--cc=arunp@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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).