[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e9ecbd0b-8741-1e7d-ae7a-f839287cb5c9@marcan.st>
Date: Sun, 2 Jan 2022 23:18:04 +0900
From: Hector Martin <marcan@...can.st>
To: Dmitry Osipenko <digetx@...il.com>,
Kalle Valo <kvalo@...eaurora.org>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Len Brown <lenb@...nel.org>,
Arend van Spriel <aspriel@...il.com>,
Franky Lin <franky.lin@...adcom.com>,
Hante Meuleman <hante.meuleman@...adcom.com>,
Chi-hsien Lin <chi-hsien.lin@...ineon.com>,
Wright Feng <wright.feng@...ineon.com>,
Chung-hsien Hsu <chung-hsien.hsu@...ineon.com>
Cc: Sven Peter <sven@...npeter.dev>,
Alyssa Rosenzweig <alyssa@...enzweig.io>,
Mark Kettenis <kettenis@...nbsd.org>,
Rafał Miłecki <zajec5@...il.com>,
Pieter-Paul Giesberts <pieter-paul.giesberts@...adcom.com>,
Linus Walleij <linus.walleij@...aro.org>,
Hans de Goede <hdegoede@...hat.com>,
"John W. Linville" <linville@...driver.com>,
"Daniel (Deognyoun) Kim" <dekim@...adcom.com>,
"brian m. carlson" <sandals@...stytoothpaste.net>,
linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-acpi@...r.kernel.org, brcm80211-dev-list.pdl@...adcom.com,
SHA-cyfmac-dev-list@...ineon.com
Subject: Re: [PATCH 03/34] brcmfmac: firmware: Support having multiple alt
paths
On 2022/01/02 15:45, Dmitry Osipenko wrote:
> 26.12.2021 18:35, Hector Martin пишет:
>> -static char *brcm_alt_fw_path(const char *path, const char *board_type)
>> +static const char **brcm_alt_fw_paths(const char *path, const char *board_type)
>> {
>> char alt_path[BRCMF_FW_NAME_LEN];
>> + char **alt_paths;
>> char suffix[5];
>>
>> strscpy(alt_path, path, BRCMF_FW_NAME_LEN);
>> @@ -609,27 +612,46 @@ static char *brcm_alt_fw_path(const char *path, const char *board_type)
>> strlcat(alt_path, board_type, BRCMF_FW_NAME_LEN);
>> strlcat(alt_path, suffix, BRCMF_FW_NAME_LEN);
>>
>> - return kstrdup(alt_path, GFP_KERNEL);
>> + alt_paths = kzalloc(sizeof(char *) * 2, GFP_KERNEL);
>
> array_size()?
Of what array?
>
>> + alt_paths[0] = kstrdup(alt_path, GFP_KERNEL);
>> +
>> + return (const char **)alt_paths;
>
> Why this casting is needed?
Because implicit conversion from char ** to const char ** is not legal
in C, as that could cause const unsoundness if you do this:
char *foo[1];
const char **bar = foo;
bar[0] = "constant string";
foo[0][0] = '!'; // clobbers constant string
But it's fine in this case since the non-const pointer disappears so
nothing can ever write through it again.
--
Hector Martin (marcan@...can.st)
Public Key: https://mrcn.st/pub
Powered by blists - more mailing lists