mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH 0/7] add proper strdup_const support
Date: Fri, 29 Nov 2024 12:59:33 +0100	[thread overview]
Message-ID: <173288157327.227234.6616084829960963757.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20241125152927.546493-1-a.fatoum@pengutronix.de>


On Mon, 25 Nov 2024 16:29:20 +0100, Ahmad Fatoum wrote:
> We currently implement strdup_const as strdup, which is correct, but
> leaves the benefits of a proper implementation on the table:
> Reducing allocations for .rodata strings, which have static storage
> duration anyway.
> 
> This series implements a proper strdup_const that avoids allocations in
> that case.
> 
> [...]

Applied, thanks!

[1/7] sandbox: hostfile: strdup device tree node names
      https://git.pengutronix.de/cgit/barebox/commit/?id=5693aac77e21 (link may not be stable)
[2/7] lds: implement is_barebox_rodata
      https://git.pengutronix.de/cgit/barebox/commit/?id=24ada94d67ae (link may not be stable)
[3/7] string: implement proper strdup_const/free_const
      https://git.pengutronix.de/cgit/barebox/commit/?id=84f699019564 (link may not be stable)
[4/7] treewide: replace basename with kbasename
      https://git.pengutronix.de/cgit/barebox/commit/?id=c71f25b2b5f2 (link may not be stable)
[5/7] treewide: use strdup_const where appropriate
      https://git.pengutronix.de/cgit/barebox/commit/?id=00943daac8d1 (link may not be stable)
[6/7] fs: efi: replace allocation with local buffer
      https://git.pengutronix.de/cgit/barebox/commit/?id=cfbf80529c4c (link may not be stable)
[7/7] cdev: fix string leaks in devfs links
      https://git.pengutronix.de/cgit/barebox/commit/?id=2f8bac45ed59 (link may not be stable)

Best regards,
-- 
Sascha Hauer <s.hauer@pengutronix.de>




      parent reply	other threads:[~2024-11-29 12:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-25 15:29 Ahmad Fatoum
2024-11-25 15:29 ` [PATCH 1/7] sandbox: hostfile: strdup device tree node names Ahmad Fatoum
2024-11-25 15:29 ` [PATCH 2/7] lds: implement is_barebox_rodata Ahmad Fatoum
2024-11-25 15:29 ` [PATCH 3/7] string: implement proper strdup_const/free_const Ahmad Fatoum
2024-11-25 15:29 ` [PATCH 4/7] treewide: replace basename with kbasename Ahmad Fatoum
2024-11-25 15:29 ` [PATCH 5/7] treewide: use strdup_const where appropriate Ahmad Fatoum
2024-11-25 15:29 ` [PATCH 6/7] fs: efi: replace allocation with local buffer Ahmad Fatoum
2024-11-25 15:29 ` [PATCH 7/7] cdev: fix string leaks in devfs links Ahmad Fatoum
2024-11-29 11:59 ` Sascha Hauer [this message]

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=173288157327.227234.6616084829960963757.b4-ty@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.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