[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aa565fea-b1c4-9b5c-73ed-591244afee19@web.de>
Date: Thu, 16 Apr 2020 08:26:43 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Mathieu Poirier <mathieu.poirier@...aro.org>,
linux-remoteproc@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, Alex Elder <elder@...aro.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Ohad Ben-Cohen <ohad@...ery.com>, Suman Anna <s-anna@...com>
Subject: Re: [PATCH v2 5/7] remoteproc: Restructure firmware name allocation
…
> +++ b/drivers/remoteproc/remoteproc_core.c
> @@ -1984,14 +1984,14 @@ static int rproc_alloc_firmware(struct rproc *rproc,
> {
> const char *p;
>
> - if (!firmware)
> + if (firmware)
> + p = kstrdup_const(firmware, GFP_KERNEL);
> + else
> /*
> * If the caller didn't pass in a firmware name then
> * construct a default name.
> */
> p = kasprintf(GFP_KERNEL, "rproc-%s-fw", name);
> - else
> - p = kstrdup_const(firmware, GFP_KERNEL);
Can the use of the conditional operator make sense at such source code places?
p = firmware ? kstrdup_const(…) : kasprintf(…);
Regards,
Markus
Powered by blists - more mailing lists