netdev - Re: ieee802154: pull requests for ieee802154/mac802154 branches

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:	Sun, 3 Aug 2014 21:29:26 +0200
From:	Alexander Aring <alex.aring@...il.com>
To:	linville@...driver.com
Cc:	marcel@...tmann.org, davem@...emloft.net, netdev@...r.kernel.org
Subject: Re: ieee802154: pull requests for ieee802154/mac802154 branches

Hi,

ping?

I talked with Marcel today and he would accept pull request for
net/ieee802154 and net/mac802154 work. I will catch all patches from the
newly generated linux-wpan (IEEE 802.15.4/IEEE 802.15.4 6LoWPAN) list.

I would base my repository on bluetooth/bluetooth-next branches then.

This option is better, because there exist shared 6LoWPAN code which is
used by bluetooth and 802154.

David and John, is this okay for you? The alternative would be that I
send pull request to wireless, but then we have the net/6lowpan
conflicts issue. Bluetooth and 802154 should have the net/6lowpan
directory mostly up-to-date.

If this is fine, can I take all patches for net/mac802154 and net/ieee802154?
So no patches for this going into net-next/net to avoid conflicts.

For the net/6lowpan branch all patches should go into
bluetooth/bluetooth-next. Please let me know if this is fine.

Thanks.

- Alex
--
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