From: Sascha Hauer <s.hauer@pengutronix.de>
To: Roland Hieber <rhi@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] common: state: fix alignment
Date: Mon, 7 Jan 2019 08:41:48 +0100 [thread overview]
Message-ID: <20190107074148.l3ahbtektf5zxox5@pengutronix.de> (raw)
In-Reply-To: <20190104151644.12393-1-rhi@pengutronix.de>
On Fri, Jan 04, 2019 at 04:16:44PM +0100, Roland Hieber wrote:
> Fixes: 7126dffd0be ("common: state: Add variable_type to state_variable")
> Signed-off-by: Roland Hieber <rhi@pengutronix.de>
> ---
> common/state/state_variables.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
Applied, thanks
Sascha
>
> diff --git a/common/state/state_variables.c b/common/state/state_variables.c
> index 269d175874..50cffba700 100644
> --- a/common/state/state_variables.c
> +++ b/common/state/state_variables.c
> @@ -132,7 +132,7 @@ static struct state_variable *state_uint8_create(struct state *state,
> static struct state_variable *state_uint32_create(struct state *state,
> const char *name,
> struct device_node *node,
> - const struct variable_type *vtype)
> + const struct variable_type *vtype)
> {
> struct state_uint32 *su32;
> struct param_d *param;
> @@ -223,7 +223,7 @@ static int state_enum32_import(struct state_variable *sv,
> static struct state_variable *state_enum32_create(struct state *state,
> const char *name,
> struct device_node *node,
> - const struct variable_type *vtype)
> + const struct variable_type *vtype)
> {
> struct state_enum32 *enum32;
> int ret, i, num_names;
> @@ -307,7 +307,7 @@ static int state_mac_import(struct state_variable *sv, struct device_node *node)
> static struct state_variable *state_mac_create(struct state *state,
> const char *name,
> struct device_node *node,
> - const struct variable_type *vtype)
> + const struct variable_type *vtype)
> {
> struct state_mac *mac;
> int ret;
> @@ -409,7 +409,7 @@ static int state_string_get(struct param_d *p, void *priv)
> static struct state_variable *state_string_create(struct state *state,
> const char *name,
> struct device_node *node,
> - const struct variable_type *vtype)
> + const struct variable_type *vtype)
> {
> struct state_string *string;
> uint32_t start_size[2];
> --
> 2.19.1
>
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
>
--
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
next prev parent reply other threads:[~2019-01-07 7:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 15:16 Roland Hieber
2019-01-07 7:41 ` Sascha Hauer [this message]
2019-01-07 14:43 ` [PATCH] common: state: fix another alignment Roland Hieber
2019-01-08 15:18 ` Sascha Hauer
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=20190107074148.l3ahbtektf5zxox5@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=rhi@pengutronix.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