deepblue/ipmitool
1
0
Fork 0
mirror of https://github.com/ipmitool/ipmitool.git synced 2026-06-25 14:51:35 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

general: Fix several misspellings

Browse Source 
Fix misspellings found by codespell in code comments,
console output and documentation.

Resolves ipmitool/ipmitool#28
This commit is contained in:
Thorsten Horstmann
2018-08-06 14:59:06 +02:00
committed by Alexander Amelkin
parent a8f3413dc2
commit 232773d171
39 changed files with 149 additions and 149 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
src/plugins/imb/imbapi.c
View File

@@ -281,7 +281,7 @@ ipmi_close_ia(void)
* @lpcbBytesReturned, address of actual bytes of output
* @lpoOverlapped address of overlapped struct
*
* returns - FALSE for fail and TRUE for success. Same as standarad NTOS call as
* returns - FALSE for fail and TRUE for success. Same as standard NTOS call as
* it also sets Ntstatus.status.
*/
static BOOL
@@ -312,7 +312,7 @@ DeviceIoControl(HANDLE dummey_hDevice, DWORD dwIoControlCode, LPVOID
s.cbOutBuffer = cbOutBuffer;
s.lpcbBytesReturned = lpcbBytesReturned;
s.lpoOverlapped = lpoOverlapped;
/* dummy place holder. Linux IMB driver doesnt return status or info
/* dummy place holder. Linux IMB driver doesn't return status or info
* via it
*/
s.ntstatus = (LPVOID)&NTstatus;
@@ -434,7 +434,7 @@ SendTimedI2cRequest(I2CREQUESTDATA *reqPtr, int timeOut, BYTE *respDataPtr,
* @responseDataLen
* @timeOut - how long to wait, in mSec units
*
* retruns - OK else error status code
* returns - OK else error status code
*/
ACCESN_STATUS
SendTimedEmpMessageResponse (ImbPacket *ptr, char *responseDataBuf,
@@ -514,7 +514,7 @@ SendTimedEmpMessageResponse (ImbPacket *ptr, char *responseDataBuf,
* @timeOut - how long to wait, in mSec units
* @sessionHandle - This is introduced in IPMI1.5,this is required to be sent in
* sendd message command as a parameter, which is then used by BMC
* to identify the correct DPC session to send the mesage to.
* to identify the correct DPC session to send the message to.
* @channelNumber - There are 3 different channels on which DPC communication
* goes on:
* * Emp - 1
@@ -591,7 +591,7 @@ SendTimedEmpMessageResponse_Ex (ImbPacket *ptr, char *responseDataBuf, int
req->req.data[i++] = ((ptr->seqLn & 0xfc) | (ptr->nfLn & 0x3));
/* The next byte is the command like get software ID(00). */
req->req.data[i++] = ptr->cmd;
/* after the cmd the data, which is sent by DPC & is retrived using the
/* after the cmd the data, which is sent by DPC & is retrieved using the
* get message earlier is sent back to DPC.
*/
for (j = 0; j < responseDataLen; ++j, ++i) {
@@ -728,7 +728,7 @@ SendTimedLanMessageResponse(ImbPacket *ptr, char *responseDataBuf,
* @timeOut - how long to wait, in mSec units
* @sessionHandle - This is introduced in IPMI1.5,this is required to be sent in
* send message command as a parameter,which is then used by BMC to identify the
* correct DPC session to send the mesage to.
* correct DPC session to send the message to.
* @channelNumber - There are 3 different channels on which DPC communication
* goes on:
* * Emp - 1
@@ -806,7 +806,7 @@ SendTimedLanMessageResponse_Ex(ImbPacket *ptr, char *responseDataBuf, int
req->req.data[i++] = ((ptr->seqLn & 0xfc) | (ptr->nfLn & 0x3));
/* The next byte is the command like get software ID(00). */
req->req.data[i++] = ptr->cmd;
/* After the cmd the data ,which is sent by DPC & is retrived using the
/* After the cmd the data ,which is sent by DPC & is retrieved using the
* get message earlier is sent back to DPC.
*/
for (j = 0; j < responseDataLen; ++j, ++i) {

6
src/plugins/imb/imbapi.h
View File

@@ -261,7 +261,7 @@ typedef struct {
#define SD_POWER_OFF 2
#pragma pack(1)
/*
* This is the generic IMB packet format, the final checksum cant be
* This is the generic IMB packet format, the final checksum can't be
* represented in this structure and will show up as the last data byte
*/
typedef struct {
@@ -318,7 +318,7 @@ typedef struct {
} ImbRequest;
typedef struct {
DWORD flags; /* request flags*/
#define NO_RESPONSE_EXPECTED 0x01 /*dont wait around for an IMB response*/
#define NO_RESPONSE_EXPECTED 0x01 /*don't wait around for an IMB response*/
DWORD timeOut; /* in uSec units*/
ImbRequest req; /* message buffer*/
} ImbRequestBuffer;
@@ -541,7 +541,7 @@ typedef struct
*/
#define ASYNC_SEQ_START 0
/*
* This is the generic IMB packet format, the final checksum cant be
* This is the generic IMB packet format, the final checksum can't be
* represented in this structure and will show up as the last data byte
*/
/*

8
src/plugins/lan/lan.c
View File

@@ -733,7 +733,7 @@ ipmi_lan_build_cmd(struct ipmi_intf * intf, struct ipmi_rq * req, int isRetry)
}
else
{
// We dont have this request in the list so we can add it
// We don't have this request in the list so we can add it
// to the list
entry = ipmi_req_add_entry(intf, req, curr_seq);
if (entry == NULL)
@@ -965,14 +965,14 @@ ipmi_lan_send_cmd(struct ipmi_intf * intf, struct ipmi_rq * req)
// This is the corner case where the remote controller responds very slowly.
//
// Example: We have to send command 23 and 2d.
// If we send command,seq as 23,10 and if we dont get any response it will
// If we send command,seq as 23,10 and if we don't get any response it will
// retry 4 times with 23,10 and then come out here and indicate that there is no
// response from the remote controller and will send the next command for
// ie 2d,11. And if the BMC is slow to respond and returns 23,10 then it
// will match it in the list and will take response of command 23 as response
// for command 2d and return success. So ideally when retries are done and
// are out of this function we should be clearing the list to be safe so that
// we dont match the old response with new request.
// we don't match the old response with new request.
// [23, 10] --> BMC
// [23, 10] --> BMC
// [23, 10] --> BMC
@@ -1437,7 +1437,7 @@ check_sol_packet_for_new_data(struct ipmi_intf * intf,
}
/*
*Rember the data for next round
* Remember the data for next round
*/
if (rsp && rsp->payload.sol_packet.packet_sequence_number)
{

4
src/plugins/lanplus/README.sol
View File

@@ -35,8 +35,8 @@ honored by ipmitool.
Note that one way that SOL communication differs from standard IPMI
commands, is that it is not simply a request response protocol. Packets
may be returned asyncrhonously from the BMC. When establishing a SOL
session, ipmitool registers a callback for asynchonously received data.
may be returned asynchronously from the BMC. When establishing a SOL
session, ipmitool registers a callback for asynchronously received data.
This call back simply prints text returned from the BMC.
Once a user has chosen to exit the SOL session (with ~.) ipmitool sends the

6
src/plugins/lanplus/lanplus.c
View File

@@ -967,7 +967,7 @@ read_open_session_response(struct ipmi_rs * rsp, int offset)
*
* param rsp [in/out] reading from the data variable and writing to the rakp 2
* section
* param offset [in] tells us where hte rakp2 payload starts
* param offset [in] tells us where the rakp2 payload starts
* param auth_alg [in] describes the authentication algorithm was agreed upon in
* the open session request/response phase. We need to know that here so
* that we know how many bytes (if any) to read fromt the packet.
@@ -1054,7 +1054,7 @@ read_rakp2_message(
*
* param rsp [in/out] reading from the data variable and writing to the rakp
* 4 section
* param offset [in] tells us where hte rakp4 payload starts
* param offset [in] tells us where the rakp4 payload starts
* param integrity_alg [in] describes the authentication algorithm was
* agreed upon in the open session request/response phase. We need
* to know that here so that we know how many bytes (if any) to read
@@ -2571,7 +2571,7 @@ check_sol_packet_for_new_data(
/*
*Rember the data for next round
* Remember the data for next round
*/
if (rsp->payload.sol_packet.packet_sequence_number)
{

2
src/plugins/lanplus/lanplus.h
View File

@@ -113,7 +113,7 @@
/*
*This is accurate, as long as we're only passing 1 auth algorithm,
* one integrity algorithm, and 1 encyrption alogrithm
* one integrity algorithm, and 1 encyrption algorithm
*/
#define IPMI_OPEN_SESSION_REQUEST_SIZE 32
#define IPMI_RAKP1_MESSAGE_SIZE 44

6
src/plugins/lanplus/lanplus_crypt.c
View File

@@ -512,7 +512,7 @@ lanplus_generate_rakp3_authcode(uint8_t * output_buffer,
* <USERNAME> - Usename (absent for null usernames)
*
* The key used to generated the SIK is Kg if Kg is not null (two-key logins are
* enabled). Otherwise Kuid (the user authcode) is used as the key to genereate
* enabled). Otherwise Kuid (the user authcode) is used as the key to generate
* the SIK.
*
* I am aware that the subscripts look backwards, but that is the way they are
@@ -897,7 +897,7 @@ lanplus_encrypt_payload(uint8_t crypt_alg,
*
* The authcode is computed using the specified integrity algorithm starting
* with the AuthType / Format field, and ending with the field immediately
* preceeding the authcode itself.
* preceding the authcode itself.
*
* The key key used to generate the authcode MAC is K1.
*
@@ -1029,7 +1029,7 @@ lanplus_decrypt_payload(uint8_t crypt_alg, const uint8_t * key,
bytes_decrypted);
/*
* We have to determine the payload size, by substracting the padding, etc.
* We have to determine the payload size, by subtracting the padding, etc.
* The last byte of the decrypted payload is the confidentiality pad length.
*/
conf_pad_length = decrypted_payload[bytes_decrypted - 1];

2
src/plugins/lanplus/lanplus_crypt_impl.c
View File

@@ -102,7 +102,7 @@ lanplus_rand(uint8_t * buffer, uint32_t num_bytes)
* param mac specifies the algorithm to be used, currently SHA1, SHA256 and MD5
* are supported
* param key is the key used for HMAC generation
* param key_len is the lenght of key
* param key_len is the length of key
* param d is the data to be MAC'd
* param n is the length of the data at d
* param md is the result of the HMAC algorithm

2
src/plugins/serial/serial_basic.c
View File

@@ -655,7 +655,7 @@ serial_bm_build_msg(const struct ipmi_intf * intf,
/* inner send message request is further */
inner_rq = (outer_rq + 1);
} else {
/* there is only outer send message reuest */
/* there is only outer send message request */
inner_rq = outer_rq;
}

2
src/plugins/serial/serial_terminal.c
View File

@@ -353,7 +353,7 @@ serial_flush(struct ipmi_intf * intf)
/*
* Receive IPMI response from the device
* Len: buffer size
* Returns: -1 or response lenth on success
* Returns: -1 or response length on success
*/
static int
recv_response(struct ipmi_intf * intf, unsigned char *data, int len)