Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
From:   Sudeep Holla <sudeep.holla@arm.com>
To:     linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org,
        Sudeep Holla <sudeep.holla@arm.com>
Cc:     Etienne Carriere <etienne.carriere@linaro.org>,
        Cristian Marussi <cristian.marussi@arm.com>,
        kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] firmware: arm_scmi: Fix sparse warnings in OPTEE transport driver
Date:   Tue,  5 Apr 2022 15:33:00 +0100
Message-Id: <164916896263.1245964.4982099650010775310.b4-ty@arm.com>
In-Reply-To: <20220404102419.1159705-1-sudeep.holla@arm.com>
References: <20220404102419.1159705-1-sudeep.holla@arm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Mon, 4 Apr 2022 11:24:19 +0100, Sudeep Holla wrote:
> The sparse checker complains about converting pointers between address
> spaces.  We correctly stored an __iomem pointer in struct scmi_optee_channel,
> but discarded the __iomem when returning it from get_channel_shm, causing one
> warning. Then we passed the non-__iomem pointer return from get_channel_shm
> at tow other places, where an __iomem pointer is expected, causing couple of
> other warnings
> 
> [...]

Applied to sudeep.holla/linux (fixes/scmi), thanks!

[1/1] firmware: arm_scmi: Fix sparse warnings in OPTEE transport driver
      https://git.kernel.org/sudeep.holla/c/bf36619a54

--
Regards,
Sudeep