From: Arnaud POULIQUEN <arnaud.pouliquen@foss.st.com>
To: Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: <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: Wed, 17 Jan 2024 14:24:40 +0100 [thread overview]
Message-ID: <96941fae-8341-4834-9283-4f6def47b1f0@foss.st.com> (raw)
In-Reply-To: <20240117131817.3338146-1-arnaud.pouliquen@foss.st.com>
Hi,
On 1/17/24 14:18, 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(-)
>
>
> base-commit: 0dd3ee31125508cd67f7e7172247f05b7fd1753a
I faced an issue with the ST server message that blocked a part
of the mails associated with this series. Please ignore this series,
as I will resend it.
Regards
Arnaud
next prev parent reply other threads:[~2024-01-17 13:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 13:18 [PATCH 0/2] remoteproc: stm32: Fix sparse warnings Arnaud Pouliquen
2024-01-17 13:18 ` [PATCH 1/2] remoteproc: stm32: Fix incorrect type in assignment for va Arnaud Pouliquen
2024-01-17 13:24 ` Arnaud POULIQUEN [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-17 13:53 [PATCH 0/2] remoteproc: stm32: Fix sparse warnings Arnaud Pouliquen
2024-01-23 19:01 ` Mathieu Poirier
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=96941fae-8341-4834-9283-4f6def47b1f0@foss.st.com \
--to=arnaud.pouliquen@foss.st.com \
--cc=andersson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mathieu.poirier@linaro.org \
/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).