You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nuttx.apache.org by ra...@apache.org on 2022/05/06 06:55:11 UTC
[incubator-nuttx] 07/07: net: Fix typos, update comments in Kconfigs
This is an automated email from the ASF dual-hosted git repository.
raiden00 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-nuttx.git
commit 3ddc019f8e975e8f36cd90f625d48e8c2c187d05
Author: JacobCrabill <ja...@flyvoly.com>
AuthorDate: Wed Mar 30 12:47:50 2022 -0700
net: Fix typos, update comments in Kconfigs
---
net/Kconfig | 4 ++--
net/can/Kconfig | 6 +++---
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/net/Kconfig b/net/Kconfig
index 221d39bba0..30b917956f 100644
--- a/net/Kconfig
+++ b/net/Kconfig
@@ -256,7 +256,7 @@ config NETDEV_LATEINIT
Normally, networking initialization occur in the later phase of the
boot process in the function up_initialize() when it calls the
driver initialization function, up_netinitialize(). This
- initialization occurs after a sufficient about of the OS has been
+ initialization occurs after a sufficient amount of the OS has been
initialized so that driver registration can be performed, but
before the completion of OS initialization and before the first
application is started.
@@ -272,7 +272,7 @@ config NETDEV_LATEINIT
dependencies so that the hardware is not in an appropriate
state for up_netinitialize() to be called.
- Examples of this latter situation includes such things as network
+ Examples of this latter situation include such things as network
drivers that required some setup via an I2C I/O expander, or network
drivers that depend on USB, SPI, I2C, PCI, serial, or other
interfaces that may not be ready when up_netinitialize() is normally
diff --git a/net/can/Kconfig b/net/can/Kconfig
index 9913ba8a6c..4face17871 100644
--- a/net/can/Kconfig
+++ b/net/can/Kconfig
@@ -11,10 +11,10 @@ config NET_CAN
select NET_READAHEAD
depends on NET
---help---
- Enable support for SocketCAN sockets that will permit.
+ Enable support for SocketCAN sockets.
- This logic is a WIP. Currently only fragmentary support is
- available, not enough to actually do anything of consequence.
+ This requires a lower-half driver compatible with the SocketCAN
+ API.
if NET_CAN