linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Loic Pallardy <loic.pallardy@st.com>
Cc: ohad@wizery.com, lee.jones@linaro.org,
	linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel@stlinux.com
Subject: Re: [PATCH v2 1/3] remoteproc: Modify FW_RSC_ADDR_ANY definition
Date: Tue, 6 Sep 2016 11:10:07 -0700	[thread overview]
Message-ID: <20160906181007.GC15161@tuxbot> (raw)
In-Reply-To: <1473147584-13183-2-git-send-email-loic.pallardy@st.com>

On Tue 06 Sep 00:39 PDT 2016, Loic Pallardy wrote:

> Replace 0xFFFFFFFFFFFFFFFF by -1 to fit any type.
> 
> Signed-off-by: Loic Pallardy <loic.pallardy@st.com>

Applied, thanks

> ---
>  include/linux/remoteproc.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/linux/remoteproc.h b/include/linux/remoteproc.h
> index d488f9e..80e1cba 100644
> --- a/include/linux/remoteproc.h
> +++ b/include/linux/remoteproc.h
> @@ -118,7 +118,7 @@ enum fw_resource_type {
>  	RSC_LAST	= 4,
>  };
>  
> -#define FW_RSC_ADDR_ANY (0xFFFFFFFFFFFFFFFF)
> +#define FW_RSC_ADDR_ANY (-1)
>  
>  /**
>   * struct fw_rsc_carveout - physically contiguous memory request
> -- 
> 1.9.1
> 

  reply	other threads:[~2016-09-06 18:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-06  7:39 [PATCH v2 0/3] Remoteproc: Add predefined coprocessor memory mapping support Loic Pallardy
2016-09-06  7:39 ` [PATCH v2 1/3] remoteproc: Modify FW_RSC_ADDR_ANY definition Loic Pallardy
2016-09-06 18:10   ` Bjorn Andersson [this message]
2016-09-06  7:39 ` [PATCH v2 2/3] remoteproc: core: transform struct fw_rsc_vdev_vring reserved field in pa Loic Pallardy
2016-09-06 18:10   ` Bjorn Andersson
2016-09-06  7:39 ` [PATCH v2 3/3] remoteproc: core: add rproc ops for memory allocation Loic Pallardy
2016-09-08 14:06   ` Lee Jones
2016-09-15 17:27   ` Bjorn Andersson
2016-09-16  7:47     ` loic pallardy
2016-09-16 18:12       ` Bjorn Andersson

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=20160906181007.GC15161@tuxbot \
    --to=bjorn.andersson@linaro.org \
    --cc=kernel@stlinux.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=loic.pallardy@st.com \
    --cc=ohad@wizery.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 NNTP newsgroup(s).