mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Daniel Schultz <d.schultz@phytec.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2 5/6] common: state: Add function to read state MAC
Date: Fri, 3 Nov 2017 09:19:36 +0100	[thread overview]
Message-ID: <20171103081936.egja7mwd4arkvj2m@pengutronix.de> (raw)
In-Reply-To: <1509626565-3722-5-git-send-email-d.schultz@phytec.de>

On Thu, Nov 02, 2017 at 01:42:44PM +0100, Daniel Schultz wrote:
> This API function allows to receive a copy of a MAC address from
> variables in a state.
> 
> Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
> ---
> Changes:
> 	v2: New patch
> 
>  common/state/state.c | 23 +++++++++++++++++++++++
>  include/state.h      |  2 ++
>  2 files changed, 25 insertions(+)
> 
> diff --git a/common/state/state.c b/common/state/state.c
> index 266d211..063e03e 100644
> --- a/common/state/state.c
> +++ b/common/state/state.c
> @@ -693,6 +693,29 @@ int state_get_name(const struct state *state, char const **name)
>  	return 0;
>  }
>  
> +int state_read_mac(struct state *state, const char *name, u8 *buf)
> +{
> +	struct state_variable *svar;
> +	struct state_mac *mac;
> +	int i;
> +
> +	if (!state || !name || !buf)
> +		return -EINVAL;
> +
> +	svar = state_find_var(state, name);
> +	if (IS_ERR(svar))
> +		return PTR_ERR(svar);
> +
> +	if (!strcmp(svar->type->type_name, "mac")) {

Could you add a patch before this one that adds a

enum state_variable_type {
	STATE_VARIABLE_TYPE_UINT8,
	...
};

Then add the type to struct variable_type and test for the type
rather than for the string name? I think in the longer run this will be
nicer when we get additional tests for the variable_type.

> +		mac = to_state_mac(svar);
> +		for (i = 0; i < 6; i++)
> +			buf[i] = mac->value[i];

memcpy?

> +		return 6;

So '6' is the return value for successfully calling this function. This
is the length of the MAC Address, but does this add any value? Better
use a negative error code and '0' for success.

Sascha

> +	}
> +
> +	return 0;
> +}
> +

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2017-11-03  8:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-02 12:42 [PATCH v2 1/6] ARM: boards: phytec-som-am335x: Add unified MLO Daniel Schultz
2017-11-02 12:42 ` [PATCH v2 2/6] ARM: dts: AM335x: Add state framework Daniel Schultz
2017-11-02 12:42 ` [PATCH v2 3/6] ARM: configs: am335x_defconfig: Add state config Daniel Schultz
2017-11-02 12:42 ` [PATCH v2 4/6] common: state: Add variable_type to state_variable Daniel Schultz
2017-11-03  8:12   ` Sascha Hauer
2017-11-02 12:42 ` [PATCH v2 5/6] common: state: Add function to read state MAC Daniel Schultz
2017-11-03  8:19   ` Sascha Hauer [this message]
2017-11-02 12:42 ` [PATCH v2 6/6] ARM: phytec-som-am335x: Set MAC addresses from state Daniel Schultz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171103081936.egja7mwd4arkvj2m@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=d.schultz@phytec.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox