linux-kernel - Re: [GIT PULL] arch/nios2 for v3.19

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]

Message-ID: <CA+55aFytYNBRG43u-PGVt1J0pSbza=RasCvRHWLcaegarYJzug@mail.gmail.com>
Date:	Tue, 9 Dec 2014 14:52:12 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Ley Foon Tan <lftan@...era.com>, Arnd Bergmann <arnd@...db.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	LeyFoon Tan <lftan.linux@...il.com>
Subject: Re: [GIT PULL] arch/nios2 for v3.19

On Tue, Dec 9, 2014 at 2:49 PM, Thomas Gleixner <tglx@...utronix.de> wrote:
>
> It's a bit sad that all the reviewed/acked-by information which has
> been sent throughout the review process is completely lost.

Yes. In general, it would probably be a great idea to just include
pointers to acks etc, and I can add them to the merge commit. Arnd's
ack got through simply because he replied to the pull request in time
before I pulled, but that's usually not really going to work, so just
having the maintainer gather up the acks and present them at pull time
would be a good idea.

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