From: "Seebs" <seebs@seebs.net>
To: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH pseudo 2/4] Do not pass null argument to pseudo_diag()
Date: Tue, 27 Jul 2021 10:48:15 -0500 [thread overview]
Message-ID: <20210727104815.0f0925b7@seebsdell> (raw)
In-Reply-To: <20210727114906.191837-2-dwrobel@ertelnet.rybnik.pl>
On Tue, 27 Jul 2021 13:49:04 +0200
"Damian Wrobel" <dwrobel@ertelnet.rybnik.pl> wrote:
> pseudo_diag("couldn't allocate absolute path for
> '%s'.\n",
> - path);
> + path ? path : "null");
Is there any actual code path where pseudo_root_path gets called on a
null path? I don't really object to the change, but I think that's
caught by guards elsewhere.
-s
next prev parent reply other threads:[~2021-07-27 15:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 11:49 [PATCH pseudo 1/4] Remove -fno-strict-aliasing and -Wno-deprecated-declarations Damian Wrobel
2021-07-27 11:49 ` [PATCH pseudo 2/4] Do not pass null argument to pseudo_diag() Damian Wrobel
2021-07-27 15:48 ` Seebs [this message]
2021-07-27 11:49 ` [PATCH pseudo 3/4] Use -pthread instead of -lpthread Damian Wrobel
2021-07-27 11:49 ` [PATCH pseudo 4/4] Do not return address of local variable Damian Wrobel
2021-07-27 15:47 ` [OE-core] " Seebs
2021-07-27 16:30 ` Damian Wrobel
2021-07-27 16:52 ` Seebs
2021-07-28 9:36 ` Damian Wrobel
2021-07-28 20:16 ` Seebs
2021-07-28 20:49 ` Andre McCurdy
2021-07-28 20:53 ` Seebs
2021-07-29 12:37 ` [OE-core] [PATCH pseudo 4/4] Do not return address of local variable - unverified Damian Wrobel
2021-07-29 15:08 ` Seebs
2021-07-27 15:49 ` [OE-core] [PATCH pseudo 1/4] Remove -fno-strict-aliasing and -Wno-deprecated-declarations Seebs
2021-07-27 16:35 ` Damian Wrobel
2021-07-27 16:46 ` Seebs
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=20210727104815.0f0925b7@seebsdell \
--to=seebs@seebs.net \
--cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.