All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Anson Huang <Anson.Huang@nxp.com>
Cc: aisheng.dong@nxp.com, s.hauer@pengutronix.de,
	linux-kernel@vger.kernel.org, Linux-imx@nxp.com,
	kernel@pengutronix.de, leonard.crestez@nxp.com,
	festevam@gmail.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V2] firmware: imx: Skip return value check for some special SCU firmware APIs
Date: Mon, 14 Oct 2019 20:48:51 +0800	[thread overview]
Message-ID: <20191014124849.GR12262@dragon> (raw)
In-Reply-To: <1570410959-32563-1-git-send-email-Anson.Huang@nxp.com>

On Mon, Oct 07, 2019 at 09:15:59AM +0800, Anson Huang wrote:
> The SCU firmware does NOT always have return value stored in message
> header's function element even the API has response data, those special
> APIs are defined as void function in SCU firmware, so they should be
> treated as return success always.
> 
> Signed-off-by: Anson Huang <Anson.Huang@nxp.com>

Applied, thanks.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Anson Huang <Anson.Huang@nxp.com>
Cc: s.hauer@pengutronix.de, kernel@pengutronix.de,
	festevam@gmail.com, aisheng.dong@nxp.com,
	leonard.crestez@nxp.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Linux-imx@nxp.com
Subject: Re: [PATCH V2] firmware: imx: Skip return value check for some special SCU firmware APIs
Date: Mon, 14 Oct 2019 20:48:51 +0800	[thread overview]
Message-ID: <20191014124849.GR12262@dragon> (raw)
In-Reply-To: <1570410959-32563-1-git-send-email-Anson.Huang@nxp.com>

On Mon, Oct 07, 2019 at 09:15:59AM +0800, Anson Huang wrote:
> The SCU firmware does NOT always have return value stored in message
> header's function element even the API has response data, those special
> APIs are defined as void function in SCU firmware, so they should be
> treated as return success always.
> 
> Signed-off-by: Anson Huang <Anson.Huang@nxp.com>

Applied, thanks.

  parent reply	other threads:[~2019-10-14 12:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-07  1:15 [PATCH V2] firmware: imx: Skip return value check for some special SCU firmware APIs Anson Huang
2019-10-07  1:15 ` Anson Huang
2019-10-07  8:01 ` Marco Felsch
2019-10-07  8:01   ` Marco Felsch
2019-10-08  0:48   ` Anson Huang
2019-10-08  0:48     ` Anson Huang
2019-10-09  8:24     ` Marco Felsch
2019-10-09  8:24       ` Marco Felsch
2019-10-09  8:28       ` Anson Huang
2019-10-09  8:28         ` Anson Huang
2019-10-09  8:57         ` Marco Felsch
2019-10-09  8:57           ` Marco Felsch
2019-10-09  9:00 ` Marco Felsch
2019-10-09  9:00   ` Marco Felsch
2019-10-09  9:09   ` Anson Huang
2019-10-09  9:09     ` Anson Huang
2019-10-09  9:37     ` Marco Felsch
2019-10-09  9:37       ` Marco Felsch
2019-10-14 12:48 ` Shawn Guo [this message]
2019-10-14 12:48   ` Shawn Guo

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=20191014124849.GR12262@dragon \
    --to=shawnguo@kernel.org \
    --cc=Anson.Huang@nxp.com \
    --cc=Linux-imx@nxp.com \
    --cc=aisheng.dong@nxp.com \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=leonard.crestez@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.