linux-kernel - Re: [GIT PULL 0/5] Second batch of arm-soc changes

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: <201203281459.41188.arnd@arndb.de>
Date:	Wed, 28 Mar 2012 14:59:40 +0000
From:	Arnd Bergmann <arnd@...db.de>
To:	Rob Herring <robherring2@...il.com>
Cc:	Olof Johansson <olof@...om.net>,
	Linus Torvalds <torvalds@...ux-foundation.org>, arm@...nel.org,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [GIT PULL 0/5] Second batch of arm-soc changes

On Wednesday 28 March 2012, Rob Herring wrote:
> On 03/28/2012 02:13 AM, Olof Johansson wrote:
> > There are a handful of merge conflicts on the branches, nothing that
> > should be too messy to sort out. I've described each conflict in the
> > corresponding pull request, including how we've resolved them in our
> > for-next branch.
> > 
> 
> Why isn't lakml getting copied on emails 1-5? The same thing happened
> with Arnd's pull request. Are they getting hung up for moderator approval?

For some reason, the mailing list rejected the emails with 'suspicious header'
warnings, but did not list which headers were suspicious. I think I've
had this problem before and solved it, but don't remember the solution
any more now. linux-kernel took the emails though.

	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/