linux-kernel - Re: linux-next: manual merge of the arm-current tree with Linus' tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 14 Aug 2013 12:01:01 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Russell King <rmk@....linux.org.uk>, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org, Stephen Boyd <sboyd@...eaurora.org>,
	Vince Weaver <vincent.weaver@...ne.edu>,
	Linus <torvalds@...ux-foundation.org>,
	Will Deacon <will.deacon@....com>
Subject: Re: linux-next: manual merge of the arm-current tree with Linus' tree


* Stephen Rothwell <sfr@...b.auug.org.au> wrote:

> Hi Russell,
> 
> Today's linux-next merge of the arm-current tree got a conflict in 
> arch/arm/kernel/perf_event.c between commit b88a2595b6d8 ("perf/arm: Fix 
> armpmu_map_hw_event()") from Linus' tree and commit d9f966357b14 ("ARM: 
> 7810/1: perf: Fix array out of bounds access in armpmu_map_hw_event()") 
> from the arm-current tree.
> 
> These are the same patch except for the return code (and the much more 
> comprehensive commit message in the arm-current tree version).  I fixed 
> it up (using the arm-current tree version - return -EINVAL instead of 
> -ENOENT - I have no way to guess which is right) and can carry the fix 
> as necessary (no action is required).

-EINVAL would be the better/cleaner one, so when this gets merged upstream 
we should pick up Russell's version. It does not affect functionality.

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/