From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH 0/2] remoteproc: stm32: Fix sparse warnings
Date: Tue, 23 Jan 2024 12:01:34 -0700 [thread overview]
Message-ID: <ZbANDtaHHY5CkC43@p14s> (raw)
In-Reply-To: <20240117135312.3381936-1-arnaud.pouliquen@foss.st.com>
On Wed, Jan 17, 2024 at 02:53:10PM +0100, Arnaud Pouliquen wrote:
> Fix warnings reported by sparse using make option "C=1"
>
> Arnaud Pouliquen (2):
> remoteproc: stm32: Fix incorrect type in assignment for va
> remoteproc: stm32: Fix incorrect type assignment returned by
> stm32_rproc_get_loaded_rsc_tablef
>
> drivers/remoteproc/stm32_rproc.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
I have applied this set.
Thanks,
Mathieu
>
> base-commit: 0dd3ee31125508cd67f7e7172247f05b7fd1753a
> --
> 2.25.1
>
next prev parent reply other threads:[~2024-01-23 19:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 13:53 [PATCH 0/2] remoteproc: stm32: Fix sparse warnings Arnaud Pouliquen
2024-01-17 13:53 ` [PATCH 1/2] remoteproc: stm32: Fix incorrect type in assignment for va Arnaud Pouliquen
2024-01-17 13:53 ` [PATCH 2/2] remoteproc: stm32: Fix incorrect type assignment returned by stm32_rproc_get_loaded_rsc_tablef Arnaud Pouliquen
2024-01-23 19:01 ` Mathieu Poirier [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-17 13:18 [PATCH 0/2] remoteproc: stm32: Fix sparse warnings Arnaud Pouliquen
2024-01-17 13:24 ` Arnaud POULIQUEN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZbANDtaHHY5CkC43@p14s \
--to=mathieu.poirier@linaro.org \
--cc=andersson@kernel.org \
--cc=arnaud.pouliquen@foss.st.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).