All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Julien Grall <julien.grall@linaro.org>
Cc: xen-devel@lists.xenproject.org, tim@xen.org,
	Jan Beulich <jbeulich@suse.com>,
	stefano.stabellini@citrix.com
Subject: Re: [PATCH v3 for 4.5] arm32: fix build after 063188f4b3
Date: Wed, 15 Oct 2014 09:11:29 +0100	[thread overview]
Message-ID: <1413360689.10417.80.camel@citrix.com> (raw)
In-Reply-To: <1413304323-4639-1-git-send-email-julien.grall@linaro.org>

On Tue, 2014-10-14 at 17:32 +0100, Julien Grall wrote:
> @@ -263,7 +250,7 @@ static int exynos5_cpu_up(int cpu)
>      iounmap(power);
>  
>      if ( secure_firmware )
> -        exynos_smc(SMC_CMD_CPU1BOOT, cpu, 0, 0);
> +        call_smc1(SMC_CMD_CPU1BOOT, cpu);
>  

Have you confirmed that none of these zeroes (throughout the patch, not
just here) are actually unused and not just formal parameters which
happen to be zero.

For example:

> -    return __invoke_psci_fn_smc(psci_cpu_on_nr,
> -                                cpu_logical_map(cpu), __pa(init_secondary), 0);
> +    return call_smc2(psci_cpu_on_nr, cpu_logical_map(cpu), __pa(init_secondary));

CPU_ON takes three arguments, target_cpu, entry_point_address and
context_id, so the zero here is actually the context_id parameter and
not a dummy argument.

> +#elif defined(CONFIG_ARM_64)
> +/* Not specific ARM64 macros for now */

"No specific..."

> +
> +int do_smc(register_t function_id, ...);

Stray?

Ian.

  reply	other threads:[~2014-10-15  8:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-14 16:32 [PATCH v3 for 4.5] arm32: fix build after 063188f4b3 Julien Grall
2014-10-15  8:11 ` Ian Campbell [this message]
2014-10-15 13:14   ` Julien Grall
  -- strict thread matches above, loose matches on Subject: below --
2014-10-15 14:08 Julien Grall
2014-10-15 14:13 ` Julien Grall

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=1413360689.10417.80.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien.grall@linaro.org \
    --cc=stefano.stabellini@citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xenproject.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 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.