From: Peter Geis <pgwipeout@gmail.com>
To: Peter Geis <pgwipeout@gmail.com>, Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Cc: linux-rockchip@lists.infradead.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v1] net: phy: fix motorcomm module automatic loading
Date: Mon, 28 Feb 2022 18:30:57 -0500 [thread overview]
Message-ID: <20220228233057.1140817-1-pgwipeout@gmail.com> (raw)
The sentinel compatible entry whitespace causes automatic module loading
to fail with certain userspace utilities. Fix this by removing the
whitespace and sentinel comment, which is unnecessary.
Fixes: 48e8c6f1612b ("net: phy: add driver for Motorcomm yt8511 phy")
Signed-off-by: Peter Geis <pgwipeout@gmail.com>
---
drivers/net/phy/motorcomm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/phy/motorcomm.c b/drivers/net/phy/motorcomm.c
index 7e6ac2c5e27e..1e3a4eed39bc 100644
--- a/drivers/net/phy/motorcomm.c
+++ b/drivers/net/phy/motorcomm.c
@@ -131,7 +131,7 @@ MODULE_LICENSE("GPL");
static const struct mdio_device_id __maybe_unused motorcomm_tbl[] = {
{ PHY_ID_MATCH_EXACT(PHY_ID_YT8511) },
- { /* sentinal */ }
+ {}
};
MODULE_DEVICE_TABLE(mdio, motorcomm_tbl);
--
2.25.1
next reply other threads:[~2022-02-28 23:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 23:30 Peter Geis [this message]
2022-03-01 0:14 ` [PATCH v1] net: phy: fix motorcomm module automatic loading Russell King (Oracle)
2022-03-01 0:44 ` Peter Geis
2022-04-29 12:51 ` Peter Geis
2022-04-30 15:52 ` Andrew Lunn
2022-04-30 16:31 ` Peter Geis
2022-04-30 16:48 ` Andrew Lunn
2022-04-30 20:19 ` Heiner Kallweit
2022-05-01 6:22 ` Russell King (Oracle)
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=20220228233057.1140817-1-pgwipeout@gmail.com \
--to=pgwipeout@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--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).