kopia lustrzana https://github.com/espressif/esp-idf
Merge branch 'typo_fix/fix-length-typo' into 'master'
docs: Fix length typo Closes IDFGH-5272 See merge request espressif/esp-idf!14371pull/7365/head
commit
5d82d7c6ee
|
@ -69,7 +69,7 @@ Additional information:
|
|||
|
||||
Packets with IDs 24..31 are standard packets with extendible
|
||||
structure and contain a length field.
|
||||
<ID><Lenght><Data><TimeStampDelta>
|
||||
<ID><Length><Data><TimeStampDelta>
|
||||
|
||||
Packets with IDs >= 32 always contain a length field.
|
||||
<ID><Length><Data><TimeStampDelta>
|
||||
|
|
|
@ -18,7 +18,7 @@ complicated mode which combines the two modes above:
|
|||
|
||||
The idea is that to send something to a SPI device, you allocate a
|
||||
transaction descriptor. It contains some information about the transfer
|
||||
like the lenghth, address, command etc, plus pointers to transmit and
|
||||
like the length, address, command etc, plus pointers to transmit and
|
||||
receive buffer. The address of this block gets pushed into the transmit
|
||||
queue. The SPI driver does its magic, and sends and retrieves the data
|
||||
eventually. The data gets written to the receive buffers, if needed the
|
||||
|
|
|
@ -79,7 +79,7 @@ typedef enum {
|
|||
* The initial time with reason=CPIO_RSN_FILE_INITIAL, when more data is available with
|
||||
* CPIO_RSN_FILE_MORE and finally with CPIO_RSN_FILE_END. For these calls, fileinfo
|
||||
* will again contain file information. buff will be the information contained in the
|
||||
* file at offset buff_offset, and the lenght of this buffer will be in buff_len.
|
||||
* file at offset buff_offset, and the length of this buffer will be in buff_len.
|
||||
*
|
||||
* The library guarantees to feed all file data to the callback consequitively, so
|
||||
* within the same file, the buff_offset from a call will always be (buff_offset+buff_len)
|
||||
|
|
|
@ -79,7 +79,7 @@ typedef enum {
|
|||
* The initial time with reason=CPIO_RSN_FILE_INITIAL, when more data is available with
|
||||
* CPIO_RSN_FILE_MORE and finally with CPIO_RSN_FILE_END. For these calls, fileinfo
|
||||
* will again contain file information. buff will be the information contained in the
|
||||
* file at offset buff_offset, and the lenght of this buffer will be in buff_len.
|
||||
* file at offset buff_offset, and the length of this buffer will be in buff_len.
|
||||
*
|
||||
* The library guarantees to feed all file data to the callback consequitively, so
|
||||
* within the same file, the buff_offset from a call will always be (buff_offset+buff_len)
|
||||
|
|
|
@ -1066,7 +1066,7 @@ void crypto_free_buffer(unsigned char *buf);
|
|||
* @crypto_ec_get_priv_key_der: get private key in der format
|
||||
* @key: key structure
|
||||
* @key_data: key data in charater buffer
|
||||
* @key_len = key lenght of charater buffer
|
||||
* @key_len = key length of charater buffer
|
||||
* Return : 0 if success
|
||||
*/
|
||||
int crypto_ec_get_priv_key_der(struct crypto_key *key, unsigned char **key_data, int *key_len);
|
||||
|
|
Ładowanie…
Reference in New Issue