From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 80AF93D3333; Wed, 21 Jan 2026 19:56:13 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769025373; cv=none; b=dGWsMvjPFibRCmPc0cbbWx/5/VU+HGSFiX8BqIhOsgEJvtmcSMeJISWhyx7JdXE86npufs1ox0GPHo761p0EAvqt+eBxqeRRRJMoOlGtbJOQHNVY8PTS9YsNkqEqRQRvm7jg48BeJhUunq3DDNJ6ueHxupB3b4GhCV22rvoNTGw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769025373; c=relaxed/simple; bh=VYaXfQ1rD23pD1bAcxSad5GEitHF7pQHKFVJ6pBbbIg=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=AiyRWhDYC5Z2INWx36of3UzoX4l9ZpLzaVNsA6xoJUisi41Ju9OPDWFJ19JXXaPwP1KqCcy1O738MyENsJ3BvnIwrwN1owztOMDQf4yQ/azaKNy9R6IEM3j4mNKvPkByrHOdM71aI23ezQ4IzYdRPUVpDHdcXIYRwww7DTa6wP4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=J1y+Uezu; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="J1y+Uezu" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5B3E1C4CEF1; Wed, 21 Jan 2026 19:56:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1769025372; bh=VYaXfQ1rD23pD1bAcxSad5GEitHF7pQHKFVJ6pBbbIg=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=J1y+UezuZ2qtaX6lLsrECXiwrifFA9tCDfu90y6CO5bVrL1MC+IrMHiRI8dbDmSzR KM5E/bhMBhFINA+ppXzSt7yHaTH5SGFQviKwplfVTybugc6BmJ5sRW++/+ivBAQEFc 3w9ABMLSjLlEs/aav7J2WjRqmJIZRyNpu4687oKVMVwgEBVkue3r65leSYcXhyO9D+ 1UNap+7SUXOvKhqeFD1yACxCA8rEh0xGbuxQwDdgyMDfQnxvBahzJjW7K+jVILOZeB UXT3QAE/QnYYC5uc0K4xK/01cYN6a0EKmxOuCZqPHQZJIgOWzhBNvb+j8H5GQUw3nw y5E9pnFJWDTNQ== From: Bjorn Andersson To: Konrad Dybcio , linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, Christian Marangi Cc: Dan Carpenter Subject: Re: [PATCH v2] soc: qcom: smem: fix qcom_smem_is_available and check if __smem is valid Date: Wed, 21 Jan 2026 13:56:03 -0600 Message-ID: <176902536619.1171053.12926970247037926721.b4-ty@kernel.org> X-Mailer: git-send-email 2.52.0 In-Reply-To: <20251122185002.26524-1-ansuelsmth@gmail.com> References: <20251122185002.26524-1-ansuelsmth@gmail.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit On Sat, 22 Nov 2025 19:49:56 +0100, Christian Marangi wrote: > Commit 7a94d5f31b54 ("soc: qcom: smem: better track SMEM uninitialized > state") changed the usage of __smem and init now as an error pointer > instead of NULL. > > qcom_smem_is_available() wasn't updated to reflect this change and also > .qcom_smem_remove doesn't reset it on module exit. > > [...] Applied, thanks! [1/1] soc: qcom: smem: fix qcom_smem_is_available and check if __smem is valid commit: 0f727e88b8353fd75ed3afdac95703da0d007c23 Best regards, -- Bjorn Andersson