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: ieee802154: pull requests for ieee802154/mac802154 branches
Date: Tue, 29 Jul 2014 10:28:31 +0200	[thread overview]
Message-ID: <20140729082829.GA2560@omega> (raw)

Hi,

I would like to send pull-requests for the net/ieee802154 net/mac802154
implementation.

I know that bluetooth sends pull requests to linux-wireless to avoid
merge conflicts. My question is: Which branch is the best to send pull
requests for my case. Also I like to get the permission to do that.

I can send pull requests to linux-wireless or linux-net or
linux-bluetooth.

For the linux-bluetooth option:

There exists a new branch net/6lowpan which contains shared code between
bluetooth 6LoWPAN and IEEE 802.15.4 6LoWPAN implementation. Currently
Marcel apply patches for this branch and maybe it's better that I send
pull requests to the bluetooth branch, to avoid merge conflicts with the
net/6lowpan/* implementation.

Then I would base my pull request on the bluetooth-* branches.



Or should I send the pull requests to linux-wireless? I don't know the
right option, but I think I should send pull requests to linux-wireless
and take care about "possible" merge conflicts with bluetooth.


Thanks.

- Alex

             reply	other threads:[~2014-07-29  8:28 UTC|newest]

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

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=20140729082829.GA2560@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).