netdev - Re: [PATCH 0/6] ISDN patches for net-next

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, 21 Jan 2013 17:38:10 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	tilman@...p.cc
Cc:	isdn@...ux-pingi.de, hjlipp@....de, keil@...systems.de,
	i4ldeveloper@...tserv.isdn4linux.de, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/6] ISDN patches for net-next

From: Tilman Schmidt <tilman@...p.cc>
Date: Mon, 21 Jan 2013 22:57:20 +0100 (CET)

> here's a series of six patches to the ISDN subsystem. Please consider
> for application to net-next. The last one should also go into -stable
> and is tagged "CC: stable" accordingly.

Patches 1-5 applied to net-next, patch 6 applied to 'net' and queued
up for -stable.

We don't have changes bypass 'net' and go into stable from net-next
like you intended.  We also don't use CC: stable for networking
patches, you ask me to queue them up into my -stable patch queue
for networking instead.

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html