target/openrisc: use coherent syntax in struct initialization
While initializing struct command_registration, the field's name "name" is not specified, thus relying on the fact that it is the first field declared in the struct and it's initialization value can be listed as the first one. Be coherent in the struct initialization and always use the field's name. Change-Id: I65d32870bf4d3df845db69682fe445c71642f976 Signed-off-by: Antonio Borneo <borneo.antonio@gmail.com> Reviewed-on: http://openocd.zylin.com/5012 Reviewed-by: Tomas Vanek <vanekt@fbl.cz> Tested-by: jenkins
This commit is contained in:
parent
a5fe9d6e24
commit
a18c1f289d
|
@ -1374,28 +1374,28 @@ COMMAND_HANDLER(or1k_addreg_command_handler)
|
|||
|
||||
static const struct command_registration or1k_hw_ip_command_handlers[] = {
|
||||
{
|
||||
"tap_select",
|
||||
.name = "tap_select",
|
||||
.handler = or1k_tap_select_command_handler,
|
||||
.mode = COMMAND_ANY,
|
||||
.usage = "tap_select name",
|
||||
.help = "Select the TAP core to use",
|
||||
},
|
||||
{
|
||||
"tap_list",
|
||||
.name = "tap_list",
|
||||
.handler = or1k_tap_list_command_handler,
|
||||
.mode = COMMAND_ANY,
|
||||
.usage = "tap_list",
|
||||
.help = "Display available TAP core",
|
||||
},
|
||||
{
|
||||
"du_select",
|
||||
.name = "du_select",
|
||||
.handler = or1k_du_select_command_handler,
|
||||
.mode = COMMAND_ANY,
|
||||
.usage = "du_select name",
|
||||
.help = "Select the Debug Unit core to use",
|
||||
},
|
||||
{
|
||||
"du_list",
|
||||
.name = "du_list",
|
||||
.handler = or1k_du_list_command_handler,
|
||||
.mode = COMMAND_ANY,
|
||||
.usage = "select_tap name",
|
||||
|
@ -1406,7 +1406,7 @@ static const struct command_registration or1k_hw_ip_command_handlers[] = {
|
|||
|
||||
static const struct command_registration or1k_reg_command_handlers[] = {
|
||||
{
|
||||
"addreg",
|
||||
.name = "addreg",
|
||||
.handler = or1k_addreg_command_handler,
|
||||
.mode = COMMAND_ANY,
|
||||
.usage = "addreg name addr feature group",
|
||||
|
|
Loading…
Reference in New Issue