netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: linville@tuxdriver.com
Cc: marcel@holtmann.org, davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: ieee802154: pull requests for ieee802154/mac802154 branches
Date: Sun, 3 Aug 2014 21:29:26 +0200	[thread overview]
Message-ID: <20140803192925.GA5664@omega> (raw)
In-Reply-To: <20140729082829.GA2560@omega>

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

      reply	other threads:[~2014-08-03 19:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-29  8:28 ieee802154: pull requests for ieee802154/mac802154 branches Alexander Aring
2014-08-03 19:29 ` Alexander Aring [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140803192925.GA5664@omega \
    --to=alex.aring@gmail.com \
    --cc=davem@davemloft.net \
    --cc=linville@tuxdriver.com \
    --cc=marcel@holtmann.org \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).