linux-kernel - Re: linux-next: unsigned commits

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]

Date:	Mon, 6 Dec 2010 23:34:58 +0000
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: unsigned commits

On Tue, Dec 07, 2010 at 10:33:46AM +1100, Stephen Rothwell wrote:
> Hi Matthew,
> 
> Looking through the drivers-x86 tree update for linux-next today, I found
> a few commits that have no signed-off-by line ...
> 
> 8f2e88b22a4caaebcc8d5a9e00a8249fec350cf3	"Generic key reporting"
> e3a2b10707902bcf95d022a5bab8f13b26bccc64	"ACPI-ify"
> 52f4e59f269e0d3bb1d54ca654d9cbf6880e7370	"Fix some tos1900 devices"
> 64ea4efdd949c99d9206a44a43984d2e861350f1	"wwan rfkill stubs"
> 
> And I think those commit messages could do with some elaboration as well.

They're somewhat WIP - I'll shift them to a topic branch.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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/