[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87pn2arw69.fsf@codeaurora.org>
Date: Tue, 12 Jan 2021 17:50:54 +0200
From: Kalle Valo <kvalo@...eaurora.org>
To: Takashi Iwai <tiwai@...e.de>
Cc: linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
Luca Coelho <luciano.coelho@...el.com>
Subject: Re: [PATCH 2/2] iwlwifi: dbg: Mark ucode tlv data as const
Takashi Iwai <tiwai@...e.de> writes:
> The ucode TLV data may be read-only and should be treated as const
> pointers, but currently a few code forcibly cast to the writable
> pointer unnecessarily. This gave developers a wrong impression as if
> it can be modified, resulting in crashing regressions already a couple
> of times.
>
> This patch adds the const prefix to those cast pointers, so that such
> attempt can be caught more easily in future.
>
> Signed-off-by: Takashi Iwai <tiwai@...e.de>
So this need to go to -next, right? Does this depend on patch 1 or can
this be applied independently?
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
Powered by blists - more mailing lists