linux-kernel - Re: linux-next: Trees and MAINTAINERS of random drivers?

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:	Wed, 18 Jul 2012 14:17:09 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Sedat Dilek <sedat.dilek@...il.com>
Cc:	David Woodhouse <dwmw2@...radead.org>,
	linux-next <linux-next@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Matt Mackall <mpm@...enic.com>
Subject: Re: linux-next: Trees and MAINTAINERS of random drivers?

On Wed, Jul 18, 2012 at 01:09:04PM +0200, Sedat Dilek wrote:
> [3] lists Ted as new random driver maintainer, but in [4] I found Matt
> as maintainer:
> 
> 5656 RANDOM NUMBER DRIVER
> 5657 M:      Matt Mackall <mpm@...enic.com>
> 5658 S:      Maintained
> 5659 F:      drivers/char/random.c
> 
> I do not think that this is still correct and furthermore in Ted's
> random.git#dev tree I see commits changing "drivers/char/random.c"
> file.
> So, that above block should IMHO be dropped and "F:
> drivers/char/random.c" added to [6]?

Oh, I see, I screwed up my update to the MAINTAINERS file and updated
the wrong block.  I'll fix it....

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