michaelh/zephyr
1
0
Fork 0
Code Releases Activity

doc: fix misspellings in docs

Browse source 
Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
This commit is contained in:
David B. Kinder 2017-06-13 15:16:40 -07:00 • committed by Anas Nashif
commit 547c74cb3c
5 changed files with 7 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

2
doc/dts/device_tree.rst
View file

@ -18,7 +18,7 @@ Rather than hard coding every detail of a board's hardware into the
operating system, the hardware-describing DTB is passed to the operating operating system, the hardware-describing DTB is passed to the operating
system at boot time. This allows the same compiled Linux kernel to support system at boot time. This allows the same compiled Linux kernel to support
different hardware configurations within an architecture family (e.g., ARM, different hardware configurations within an architecture family (e.g., ARM,
x86, PowerPC) and moves a significant part of the hardware description out of x86, PowerPC) and moves a significant part of the hardware description out of
the kernel binary itself. the kernel binary itself.
Traditional usage of device tree involves storing of the Device Tree Blob. Traditional usage of device tree involves storing of the Device Tree Blob.

2
doc/kernel/other/interrupts.rst
View file

@ -277,7 +277,7 @@ which case the CONFIG_GEN_IRQ_VECTOR_TABLE option should be disabled.
Some architectures may reserve some initial vectors for system exceptions Some architectures may reserve some initial vectors for system exceptions
and declare this in a table elsewhere, in which case and declare this in a table elsewhere, in which case
CONFIG_GEN_IRQ_START_VECTOR needs to be set to properly offset the indicies CONFIG_GEN_IRQ_START_VECTOR needs to be set to properly offset the indices
in the table. in the table.
SW ISR Table SW ISR Table

2
doc/porting/arch.rst
View file

@ -21,7 +21,7 @@ some are optional:
take when the CPU comes out of reset (required). take when the CPU comes out of reset (required).
* **Interrupt and exception handling**: each architecture handles asynchronous * **Interrupt and exception handling**: each architecture handles asynchronous
and un-requested events in a specific manner (required). and unrequested events in a specific manner (required).
* **Thread context switching**: the Zephyr context switch is dependent on the * **Thread context switching**: the Zephyr context switch is dependent on the
ABI and each ISA has a different set of registers to save (required). ABI and each ISA has a different set of registers to save (required).

6
doc/subsystems/networking/l2-and-drivers.rst
View file

@ -90,14 +90,14 @@ parameter here. The Ethernet L2 layer will update such information
once the packet's Ethernet header has been successfully parsed. once the packet's Ethernet header has been successfully parsed.
In case :c:func:`net_recv_data()` call fails, it will be up to the In case :c:func:`net_recv_data()` call fails, it will be up to the
device driver to un-reference the buffer via device driver to unreference the buffer via
:c:func:`net_pkt_unref()`. :c:func:`net_pkt_unref()`.
On sending, it is up to the device driver to send the buffer all at On sending, it is up to the device driver to send the buffer all at
once, with all the fragments. once, with all the fragments.
In case of a fully successful packet transmission only, the device In case of a fully successful packet transmission only, the device
driver must un-reference the buffer via `net_pkt_unref()`. driver must unreference the buffer via `net_pkt_unref()`.
Each Ethernet device driver will need, in the end, to call Each Ethernet device driver will need, in the end, to call
`NET_DEVICE_INIT_INSTANCE()` like this: `NET_DEVICE_INIT_INSTANCE()` like this:
@ -139,7 +139,7 @@ here as well. There are two specific differences however:
:c:type:`struct net_if` send function. It turn, the implementation :c:type:`struct net_if` send function. It turn, the implementation
of :c:func:`ieee802154_radio_send()` will ensure the same behavior: of :c:func:`ieee802154_radio_send()` will ensure the same behavior:
sending one fragment at a time through :c:type:`struct sending one fragment at a time through :c:type:`struct
ieee802154_radio_api` tx function, and un-referencing the buffer ieee802154_radio_api` tx function, and unreferencing the buffer
only when all the transmission were successful. only when all the transmission were successful.
Each IEEE 802.15.4 device driver, in the end, will need to call Each IEEE 802.15.4 device driver, in the end, will need to call

2
doc/subsystems/networking/network-management-api.rst
View file

@ -44,7 +44,7 @@ more events that are relevant.
Two functions are available, `net_mgmt_add_event_callback()` for Two functions are available, `net_mgmt_add_event_callback()` for
registering the callback function, and `net_mgmt_del_event_callback()` registering the callback function, and `net_mgmt_del_event_callback()`
for un-registering. A helper function, `net_mgmt_init_event_cb()`, can for unregistering. A helper function, `net_mgmt_init_event_cb()`, can
be used to ease the initialization of the callback structure. be used to ease the initialization of the callback structure.
When an event is raised that matches a registered event mask, the When an event is raised that matches a registered event mask, the