netdev - Re: linux-next: manual merge of the wireless-next tree with the net-next tree

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: <20120104.223052.902437565229260010.davem@davemloft.net>
Date:	Wed, 04 Jan 2012 22:30:52 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	Larry.Finger@...inger.net
Cc:	sfr@...b.auug.org.au, linville@...driver.com,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	rusty@...tcorp.com.au, netdev@...r.kernel.org
Subject: Re: linux-next: manual merge of the wireless-next tree with the
 net-next tree

From: Larry Finger <Larry.Finger@...inger.net>
Date: Wed, 04 Jan 2012 21:12:29 -0600

> Is there a good explanation why changes in wireless drivers are sent
> to net-next, and not wireless-testing? If that were stopped, this kind
> of conflict would be avoided.

It was a networking wide change and it's easiest if I just take it
in and deal with the merge issues.
--
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