From: David Gibson <david@gibson.dropbear.id.au>
To: Ayush Singh <ayush@beagleboard.org>
Cc: Andreas Gnau <andreas.gnau@iopsys.eu>,
d-gole@ti.com, lorforlinux@beagleboard.org,
jkridner@beagleboard.org, robertcnelson@beagleboard.org,
Andrew Davis <afd@ti.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Simon Glass <sjg@chromium.org>,
devicetree-compiler@vger.kernel.org
Subject: Re: [PATCH v2 1/4] Add alloc_marker
Date: Wed, 28 May 2025 15:13:10 +1000 [thread overview]
Message-ID: <aDabZokq7CMAUNaa@zatzit> (raw)
In-Reply-To: <20250311-previous-value-v2-1-e4a8611e956f@beagleboard.org>
[-- Attachment #1: Type: text/plain, Size: 2082 bytes --]
On Tue, Mar 11, 2025 at 09:05:37PM +0530, Ayush Singh wrote:
> - Add helper to allocate new marker
>
> Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
> Signed-off-by: Ayush Singh <ayush@beagleboard.org>
This is a reasonable cleanup regardless of anything else. Applied.
> ---
> data.c | 20 +++++++++++++++-----
> dtc.h | 2 ++
> 2 files changed, 17 insertions(+), 5 deletions(-)
>
> diff --git a/data.c b/data.c
> index 14734233ad8b7ebd38c3e62442b81aae66601806..913796f2e664d07cdc48e0cbf2ab5d6fe9978072 100644
> --- a/data.c
> +++ b/data.c
> @@ -228,11 +228,7 @@ struct data data_add_marker(struct data d, enum markertype type, char *ref)
> {
> struct marker *m;
>
> - m = xmalloc(sizeof(*m));
> - m->offset = d.len;
> - m->type = type;
> - m->ref = ref;
> - m->next = NULL;
> + m = alloc_marker(d.len, type, ref);
>
> return data_append_markers(d, m);
> }
> @@ -254,3 +250,17 @@ bool data_is_one_string(struct data d)
>
> return true;
> }
> +
> +struct marker *alloc_marker(unsigned int offset, enum markertype type,
> + char *ref)
> +{
> + struct marker *m;
> +
> + m = xmalloc(sizeof(*m));
> + m->offset = offset;
> + m->type = type;
> + m->ref = ref;
> + m->next = NULL;
> +
> + return m;
> +}
> diff --git a/dtc.h b/dtc.h
> index 4c4aaca1fc417c9d93e904e64b2c40216ee1b093..86928e1eea9764fe5d74d6dbb987589d65d54b66 100644
> --- a/dtc.h
> +++ b/dtc.h
> @@ -183,6 +183,8 @@ struct data data_append_byte(struct data d, uint8_t byte);
> struct data data_append_zeroes(struct data d, int len);
> struct data data_append_align(struct data d, int align);
>
> +struct marker *alloc_marker(unsigned int offset, enum markertype type,
> + char *ref);
> struct data data_add_marker(struct data d, enum markertype type, char *ref);
>
> bool data_is_one_string(struct data d);
>
--
David Gibson (he or they) | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you, not the other way
| around.
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-05-28 5:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 15:35 [PATCH v2 0/4] Add capability to create property from old property Ayush Singh
2025-03-11 15:35 ` [PATCH v2 1/4] Add alloc_marker Ayush Singh
2025-05-28 5:13 ` David Gibson [this message]
2025-03-11 15:35 ` [PATCH v2 2/4] srcpos: Define srcpos_free Ayush Singh
2025-05-28 5:16 ` David Gibson
2025-03-11 15:35 ` [PATCH v2 3/4] dtc: Add /./ Ayush Singh
2025-03-11 15:49 ` Andreas Gnau
2025-06-02 8:20 ` David Gibson
2025-03-11 15:35 ` [PATCH v2 4/4] tests: Add test for /./ Ayush Singh
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=aDabZokq7CMAUNaa@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=afd@ti.com \
--cc=andreas.gnau@iopsys.eu \
--cc=ayush@beagleboard.org \
--cc=d-gole@ti.com \
--cc=devicetree-compiler@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=jkridner@beagleboard.org \
--cc=lorforlinux@beagleboard.org \
--cc=robertcnelson@beagleboard.org \
--cc=sjg@chromium.org \
/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;
as well as URLs for NNTP newsgroup(s).