From: "Álvaro Fernández Rojas" <noltari@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Jonas Gorski <jonas.gorski@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Rob Herring <robh+dt@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] net: mdio: Add BCM6368 MDIO mux bus controller
Date: Mon, 15 Mar 2021 14:53:39 +0100 [thread overview]
Message-ID: <CA6D1162-FB0E-4899-8172-DB49CC522EB9@gmail.com> (raw)
In-Reply-To: <20210308115705.18c0acd5@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Hi Jakub,
> El 8 mar 2021, a las 20:57, Jakub Kicinski <kuba@kernel.org> escribió:
>
> On Mon, 8 Mar 2021 19:41:02 +0100 Álvaro Fernández Rojas wrote:
>> This controller is present on BCM6318, BCM6328, BCM6362, BCM6368 and BCM63268
>> SoCs.
>>
>> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
>
> make[2]: *** Deleting file 'Module.symvers'
> ERROR: modpost: missing MODULE_LICENSE() in drivers/net/mdio/mdio-mux-bcm6368.o
> make[2]: *** [Module.symvers] Error 1
> make[1]: *** [modules] Error 2
> make: *** [__sub-make] Error 2
> make[2]: *** Deleting file 'Module.symvers’
Ok, I’ll add the following in v2:
MODULE_AUTHOR("Álvaro Fernández Rojas <noltari@gmail.com>");
MODULE_DESCRIPTION("BCM6368 mdiomux bus controller driver");
MODULE_LICENSE("GPL v2");
next prev parent reply other threads:[~2021-03-15 13:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 18:41 [PATCH 0/2] " Álvaro Fernández Rojas
2021-03-08 18:41 ` [PATCH 1/2] dt-bindings: net: Add bcm6368-mdio-mux bindings Álvaro Fernández Rojas
2021-03-08 20:54 ` Andrew Lunn
2021-03-15 13:51 ` Álvaro Fernández Rojas
2021-03-08 18:41 ` [PATCH 2/2] net: mdio: Add BCM6368 MDIO mux bus controller Álvaro Fernández Rojas
2021-03-08 19:57 ` Jakub Kicinski
2021-03-15 13:53 ` Álvaro Fernández Rojas [this message]
2021-03-08 21:00 ` Andrew Lunn
2021-03-15 14:02 ` Álvaro Fernández Rojas
2021-03-17 17:49 ` Andrew Lunn
2021-03-17 21:42 ` Florian Fainelli
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=CA6D1162-FB0E-4899-8172-DB49CC522EB9@gmail.com \
--to=noltari@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=hkallweit1@gmail.com \
--cc=jonas.gorski@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@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
Powered by JetHome