All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Mark Rutland <Mark.Rutland@arm.com>
Subject: Re: linux-next: manual merge of the arm-perf tree with Linus' and teh arm-current trees
Date: Fri, 29 May 2015 11:21:54 +0100	[thread overview]
Message-ID: <20150529102154.GC6528@arm.com> (raw)
In-Reply-To: <20150529111432.397105d2@canb.auug.org.au>

On Fri, May 29, 2015 at 02:14:32AM +0100, Stephen Rothwell wrote:
> Today's linux-next merge of the arm-perf tree got a conflict in
> arch/arm/kernel/perf_event_cpu.c between commit 338d9dd3e2ae ("ARM:
> 8351/1: perf: don't warn about missing interrupt-affinity property for
> PPIs") from Linus' tree and 8d2812849acb ("ARM: 8357/1: perf: fix
> memory leak when probing PMU PPIs") from the arm-current tree and
> commit 64d0d3943e14 ("arm: perf: make of_pmu_irq_cfg take arm_pmu")
> from the arm-perf tree.
> 
> I fixed it up (see below) and can carry the fix as necessary (no action
> is required).

Thanks Stephen, looks good to me. I've got some more patches queued which
will actually mean we just remove this file altogether, but this is fine
for now.

Will

> -- 
> Cheers,
> Stephen Rothwell                    sfr@canb.auug.org.au
> 
> diff --cc arch/arm/kernel/perf_event_cpu.c
> index 3b8c2833c537,50f245bf4e05..000000000000
> --- a/arch/arm/kernel/perf_event_cpu.c
> +++ b/arch/arm/kernel/perf_event_cpu.c
> @@@ -301,17 -306,12 +306,18 @@@ static int probe_current_pmu(struct arm
>   	return ret;
>   }
>   
> - static int of_pmu_irq_cfg(struct platform_device *pdev)
> + static int of_pmu_irq_cfg(struct arm_pmu *pmu)
>   {
>  -	int i;
>  +	int i, irq;
> + 	struct platform_device *pdev = pmu->plat_device;
>  -	int *irqs = kcalloc(pdev->num_resources, sizeof(*irqs), GFP_KERNEL);
>  +	int *irqs;
>   
>  +	/* Don't bother with PPIs; they're already affine */
>  +	irq = platform_get_irq(pdev, 0);
>  +	if (irq >= 0 && irq_is_percpu(irq))
>  +		return 0;
>  +
>  +	irqs = kcalloc(pdev->num_resources, sizeof(*irqs), GFP_KERNEL);
>   	if (!irqs)
>   		return -ENOMEM;
>   

      reply	other threads:[~2015-05-29 10:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-29  1:14 linux-next: manual merge of the arm-perf tree with Linus' and teh arm-current trees Stephen Rothwell
2015-05-29 10:21 ` Will Deacon [this message]

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=20150529102154.GC6528@arm.com \
    --to=will.deacon@arm.com \
    --cc=Mark.Rutland@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.