linux-kernel - Re: [PATCH] ARM: msm: defconfigs for Qualcomm dev boards

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:	Tue, 30 Aug 2011 17:15:07 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	David Brown <davidb@...eaurora.org>
Cc:	Russell King <linux@....linux.org.uk>,
	linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] ARM: msm: defconfigs for Qualcomm dev boards

On Tuesday 30 August 2011, David Brown wrote:
> Add default configs for the development boards for several Qualcomm
> MSM-family chips.
> 
> Signed-off-by: David Brown <davidb@...eaurora.org>
> ---
> These are my current defconfigs for these targets.  I'd like to get
> these into next so that the targets can get build tested.  I'm not
> sure if we want to push them to mainline, since devicetree would
> theoretically eliminate the need for all of them.

I think it's reasonable to have them in mainline while the device
tree support on MSM is still incomplete, but I can also just
stick them in to a branch that I don't submit to mainline
if you prefer to have them only in linux-next.

Russell, if you want to keep the defconfig files under your
ownership, that's also fine with me. In that case:
Acked-by: Arnd Bergmann <arnd@...db.de>

	Arnd
--
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/