On Thu, Dec 15, 2016 at 10:45 PM, Hannes Frederic Sowa <hannes@xxxxxxxxxxxxxxxxxxx> wrote: > By the way, if you target net-next, it is currently closed. So no need > to hurry. Honestly I have no idea what I'm targeting. The hash function touches lib/. The secure_seq stuff touches net/. The rng stuff touches random.c. Shall this be for net-next? For lib-next (doesn't exist)? For tytso-next? Since a lot of feedback has come from netdev people, I suspect net-next is the correct answer. In that case, I'll ask Ted for his sign-off to touch random.c, and then we'll get this queued up in net-next. Please correct me if this doesn't actually resemble how things work around here... Jason -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html