trivial: Fix up some typos from codespell

This commit is contained in:
Richard Hughes 2019-11-01 14:21:20 +00:00
parent 62e7112b4e
commit 02792c0ba3
13 changed files with 14 additions and 14 deletions

View File

@ -6,7 +6,7 @@ If you have any concerns please let us know.
## Supported Versions
The `1.2.x` and `1.1.x` branches are fully supported by the upstream authors.
Additonally, the `1.0.x` branch is supported for security and bug fixes.
Additionally, the `1.0.x` branch is supported for security and bug fixes.
Older releases than this are unsupported by upstream but may be supported by
your distributor or distribution. If you open an issue with one of these older

View File

@ -130,7 +130,7 @@
<li>Fix a libasan failure when reading a UEFI variable</li>
<li>Never guess the version format from the version string</li>
<li>Only use class-based instance IDs for quirk matching</li>
<li>Prompt the user to shutdown if requried when installing by ID</li>
<li>Prompt the user to shutdown if required when installing by ID</li>
<li>Reset the forced version during DFU attach and detach</li>
</ul>
</description>

View File

@ -35,7 +35,7 @@ fu_plugin_coldplug (FuPlugin *plugin, GError **error)
g_autofree gchar *triplet = NULL;
g_autoptr(FuDevice) dev = NULL;
/* don't inlcude FU_HWIDS_KEY_BIOS_VERSION */
/* don't include FU_HWIDS_KEY_BIOS_VERSION */
static const gchar *hwids[] = {
"HardwareID-3",
"HardwareID-4",

View File

@ -42,7 +42,7 @@
* * `use-atmel-avr`: Device uses the ATMEL bootloader
* * `use-protocol-zero`: Fix up the protocol number
* * `legacy-protocol`: Use a legacy protocol version
* * `detach-for-attach`: Requries a DFU_REQUEST_DETACH to attach
* * `detach-for-attach`: Requires a DFU_REQUEST_DETACH to attach
*
* Default value: `none`
*
@ -793,7 +793,7 @@ dfu_device_ensure_interface (DfuDevice *device, GError **error)
* @error: a #GError, or %NULL
*
* Refreshes the cached properties on the DFU device. If there are any transers
* in progress thay are cancelled, and if there are any pending errors they are
* in progress they are cancelled, and if there are any pending errors they are
* cancelled.
*
* Return value: %TRUE for success

View File

@ -146,7 +146,7 @@ dfu_element_set_address (DfuElement *element, guint32 address)
* dfu_element_to_string:
* @element: a #DfuElement
*
* Returns a string representaiton of the object.
* Returns a string representation of the object.
*
* Return value: NULL terminated string, or %NULL for invalid
**/

View File

@ -308,7 +308,7 @@ dfu_firmware_write_file (DfuFirmware *firmware, GFile *file, GError **error)
* dfu_firmware_format_to_string:
* @format: a #DfuFirmwareFormat, e.g. %DFU_FIRMWARE_FORMAT_DFU
*
* Returns a string representaiton of the format.
* Returns a string representation of the format.
*
* Return value: NULL terminated string, or %NULL for invalid
**/

View File

@ -212,7 +212,7 @@ dfu_sector_cap_to_string (DfuSectorCap cap)
* dfu_sector_to_string:
* @sector: a #DfuSector
*
* Returns a string representaiton of the object.
* Returns a string representation of the object.
*
* Return value: NULL terminated string, or %NULL for invalid
**/

View File

@ -494,7 +494,7 @@ fu_qmi_pdc_updater_activate_config_ready (GObject *qmi_client, GAsyncResult *res
output = qmi_client_pdc_activate_config_finish (QMI_CLIENT_PDC (qmi_client), res, &ctx->error);
if (output == NULL) {
/* If we didn't receive a response, this is a good indication that the device
* reseted itself, we can consider this a successful operation.
* reset itself, we can consider this a successful operation.
* Note: not using g_error_matches() to avoid matching the domain, because the
* error may be either QMI_CORE_ERROR_TIMEOUT or MBIM_CORE_ERROR_TIMEOUT (same
* numeric value), and we don't want to build-depend on libmbim just for this.

View File

@ -360,7 +360,7 @@ fu_solokey_device_get_version_bl (FuSolokeyDevice *self, GError **error)
g_autoptr(GByteArray) req = g_byte_array_new ();
g_autoptr(GByteArray) res = NULL;
/* pass thru data */
/* pass through data */
fu_solokey_device_exchange (req, SOLO_BOOTLOADER_VERSION, 0x00, NULL);
res = fu_solokey_device_packet (self, SOLO_BOOTLOADER_HID_CMD_BOOT, req, error);
if (res == NULL)

View File

@ -811,7 +811,7 @@ fu_synaptics_rmi_device_wait_for_idle (FuSynapticsRmiDevice *self,
/* if for some reason we are not getting attention reports for HID devices
* then we can still continue after the timeout and read F34 status
* but if we have to wait for the timeout to ellapse everytime then this
* but if we have to wait for the timeout to ellapse every time then this
* will be slow */
if (priv->f34->function_version == 0x1) {
res = fu_synaptics_rmi_device_read (self, priv->flash.status_addr, 0x2, error);

View File

@ -12,7 +12,7 @@ Plugin = synapticsmst
# * Will map to a GUID containing HwID product SKU
# * These GUIDs will look like MST-${PRODUCTSKU}-${BOARDID}
# DeviceKind != system
# * Will map to a GUID containing each comma delimitted substring
# * Will map to a GUID containing each comma delimited substring
# * These GUIDs will look like MST-${DEVICEKIND}-${CHIPID}-${BOARDID}
#
# By default the Synaptics MST device will restart after update

View File

@ -44,7 +44,7 @@ This plugin uses the following plugin-specific quirks:
| `SpiCmdReadIdSz` | Size of the ReadId response | 1.3.3 |
The `SpiCmdReadId` and `SpiCmdReadIdSz` quirks have to be assigned to the device
instance attribute, rather then the flash part as the ID is requried to query
instance attribute, rather then the flash part as the ID is required to query
the other flash chip parameters. For example:
[DeviceInstanceId=USB\VID_2109&PID_0210]

View File

@ -693,7 +693,7 @@ fu_util_firmware_read (FuUtilPrivate *priv, gchar **values, GError **error)
return FALSE;
}
/* write a zero lenth file to ensure the destination is writable to
/* write a zero length file to ensure the destination is writable to
* avoid failing at the end of a potentially lengthy operation */
if (!fu_common_set_contents_bytes (values[0], blob_empty, error))
return FALSE;