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] [thread-next>] [day] [month] [year] [list]
Message-ID: <1300890191.6117.43.camel@m0nster>
Date:	Wed, 23 Mar 2011 07:23:11 -0700
From:	Daniel Walker <dwalker@...o99.com>
To:	David Brown <davidb@...eaurora.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org,
	Bryan Huntsman <bryanh@...eaurora.org>
Subject: Re: [Git pull] MSM for v2.6.39

On Thu, 2011-03-17 at 08:59 -0700, David Brown wrote:
> David Brown (16):
>       msm: Add CPU queries
>       msm: Generalize timer register mappings
>       msm: Generalize QGIC registers
>       msm: Add MSM 8960 cpu_is check
>       Merge branch 'msm-uart' into for-next
>       Merge branch 'msm-8960' into for-next
>       Merge branch 'msm-sdcc' into for-next
>       Merge branch 'msm-fb' into for-next
>       Merge branch 'msm-8960' into msm-core
>       msm: Remove broken register definition from trout
>       msm: Warning fix in trout gpio board file
>       Merge branch 'msm-core' into for-next
>       Merge branch 'msm-core' into for-next
>       Merge branch 'msm-core' into for-next
>       msm: Use explicit GPLv2 licenses
>       Merge remote branch 'rmk/for-linus' into for-linus 

Could you change the "for-next" name to something more interesting like
msm-for-linus .. I think it would be acceptable to just create
msm-for-linus during the merge window and merge all the sub-tree's into
that.

Daniel

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ