History

amt: fix wrong type string definition

amt message type definition starts from 1, not 0. But type_str[] starts from 0. So, it prints wrong type information.

Taehee Yoo committed 4 years ago

Commit d7970031 parent d16207f1 file · +1 −0Browse files

Unified · Split

drivers/net/amt.c+1−0
@@ -51,6 +51,7 @@ static char *status_str[] = { · 50 unmodified lines
5151 };
5252
5353 static char *type_str[] = {
54+ "", /* Type 0 is not defined */
5455 "AMT_MSG_DISCOVERY",
5556 "AMT_MSG_ADVERTISEMENT",
5657 "AMT_MSG_REQUEST",

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t