All of lore.kernel.org
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, Alexander Couzens <lynxis@fe80.eu>,
	Daniel Golle <daniel@makrotopia.org>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	netdev@vger.kernel.org,
	"open list:ARM/Mediatek SoC support"
	<linux-kernel@vger.kernel.org>,
	"moderated list:ARM/Mediatek SoC support"
	<linux-arm-kernel@lists.infradead.org>,
	"moderated list:ARM/Mediatek SoC support"
	<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH net-next 10/10] net: fill in MODULE_DESCRIPTION()s for PCS Layer
Date: Wed, 10 Jan 2024 03:48:08 -0800	[thread overview]
Message-ID: <ZZ6D+AylYTNDW9F9@gmail.com> (raw)
In-Reply-To: <cf825e28-cceb-49e1-9880-7971cc955b2c@lunn.ch>

On Mon, Jan 08, 2024 at 08:21:03PM +0100, Andrew Lunn wrote:
> On Mon, Jan 08, 2024 at 10:16:10AM -0800, Breno Leitao wrote:
> > W=1 builds now warn if module is built without a MODULE_DESCRIPTION().
> > Add descriptions to the LynxI PCS MediaTek's SoC.
> 
> Does pcs-lynx.c also have this issue? It can be built at a module.

Absolutely. I can see the warning in pcs-lynx and pcs-pts.

WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/net/pcs/pcs_xpcs.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/net/pcs/pcs-lynx.o


WARNING: multiple messages have this Message-ID (diff)
From: Breno Leitao <leitao@debian.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, Alexander Couzens <lynxis@fe80.eu>,
	Daniel Golle <daniel@makrotopia.org>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	netdev@vger.kernel.org,
	"open list:ARM/Mediatek SoC support"
	<linux-kernel@vger.kernel.org>,
	"moderated list:ARM/Mediatek SoC support"
	<linux-arm-kernel@lists.infradead.org>,
	"moderated list:ARM/Mediatek SoC support"
	<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH net-next 10/10] net: fill in MODULE_DESCRIPTION()s for PCS Layer
Date: Wed, 10 Jan 2024 03:48:08 -0800	[thread overview]
Message-ID: <ZZ6D+AylYTNDW9F9@gmail.com> (raw)
In-Reply-To: <cf825e28-cceb-49e1-9880-7971cc955b2c@lunn.ch>

On Mon, Jan 08, 2024 at 08:21:03PM +0100, Andrew Lunn wrote:
> On Mon, Jan 08, 2024 at 10:16:10AM -0800, Breno Leitao wrote:
> > W=1 builds now warn if module is built without a MODULE_DESCRIPTION().
> > Add descriptions to the LynxI PCS MediaTek's SoC.
> 
> Does pcs-lynx.c also have this issue? It can be built at a module.

Absolutely. I can see the warning in pcs-lynx and pcs-pts.

WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/net/pcs/pcs_xpcs.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/net/pcs/pcs-lynx.o


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2024-01-10 11:48 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08 18:16 [PATCH net-next 00/10] Fix MODULE_DESCRIPTION() for net (p1) Breno Leitao
2024-01-08 18:16 ` [PATCH net-next 01/10] net: fill in MODULE_DESCRIPTION()s for 8390 Breno Leitao
2024-01-09 11:25   ` Geert Uytterhoeven
2024-01-09 14:29     ` Breno Leitao
2024-01-08 18:16 ` [PATCH net-next 02/10] net: fill in MODULE_DESCRIPTION()s for SLIP Breno Leitao
2024-01-08 18:16 ` [PATCH net-next 03/10] net: fill in MODULE_DESCRIPTION()s for HSR Breno Leitao
2024-01-08 18:16 ` [PATCH net-next 04/10] net: fill in MODULE_DESCRIPTION()s for NFC Breno Leitao
2024-01-08 18:57   ` Krzysztof Kozlowski
2024-01-08 18:16 ` [PATCH net-next 05/10] net: fill in MODULE_DESCRIPTION()s for Sun RPC Breno Leitao
2024-01-08 21:49   ` Jeff Layton
2024-01-08 18:16 ` [PATCH net-next 06/10] net: fill in MODULE_DESCRIPTION()s for ieee802154 Breno Leitao
2024-01-09  7:25   ` Stefan Schmidt
2024-01-09 14:29     ` Breno Leitao
2024-01-24 16:48     ` Miquel Raynal
2024-01-25 10:00       ` Breno Leitao
2024-01-08 18:16 ` [PATCH net-next 07/10] net: fill in MODULE_DESCRIPTION()s for 6LoWPAN Breno Leitao
2024-01-10  1:04   ` Alexander Aring
2024-01-10  1:05     ` Alexander Aring
2024-01-10  9:19     ` Breno Leitao
2024-01-08 18:16 ` [PATCH net-next 08/10] net: fill in MODULE_DESCRIPTION()s for ds26522 module Breno Leitao
2024-01-08 18:16 ` [PATCH net-next 09/10] net: fill in MODULE_DESCRIPTION()s for s2io Breno Leitao
2024-01-08 18:16 ` [PATCH net-next 10/10] net: fill in MODULE_DESCRIPTION()s for PCS Layer Breno Leitao
2024-01-08 18:16   ` Breno Leitao
2024-01-08 19:21   ` Andrew Lunn
2024-01-08 19:21     ` Andrew Lunn
2024-01-10 11:48     ` Breno Leitao [this message]
2024-01-10 11:48       ` Breno Leitao
2024-01-09  8:01 ` [PATCH net-next 00/10] Fix MODULE_DESCRIPTION() for net (p1) Paolo Abeni
2024-01-12  0:14 ` Jakub Kicinski
2024-01-12  0:30 ` patchwork-bot+netdevbpf

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=ZZ6D+AylYTNDW9F9@gmail.com \
    --to=leitao@debian.org \
    --cc=andrew@lunn.ch \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=daniel@makrotopia.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=lynxis@fe80.eu \
    --cc=matthias.bgg@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.