linux-kernel - Re: linux-next: Tree for Jun 23

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: <87twty66gp.fsf@x220.int.ebiederm.org>
Date:	Tue, 23 Jun 2015 05:53:58 -0500
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: linux-next: Tree for Jun 23

Stephen could you please drop the kdbus tree?

There was some significant work that was identified last merge window
that has not yet been done, and who knows when it will be done.
Certainly the recent sd-bus API announcement strongly suggests that
there are no plans to perform such work.

Having the kdbus tree in linux-next with the implicit suggestion that a
pull request will be sent to Linus this merge window before the problems
are addressed and we will have to repeat the mess from last merge window
keeps me up at night.

So to avoid the appearance that the kdbus folks are continuing to
ignoring feedback can we please keep the kdbus tree out of linux-next
until it is ready to be merged?

Thank you,
Eric
--
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/