From: Alexander Aring <alex.aring@gmail.com>
To: linux-wpan@vger.kernel.org
Subject: new handling for applying patches
Date: Tue, 7 Oct 2014 09:40:27 +0200 [thread overview]
Message-ID: <20141007074025.GA2768@omega> (raw)
Hi,
over irc, means:
irc.freenode.net #linux-wireless (there exist also a #linux-wpan channel)
Marcel offered this:
<qoute>
20:04 < holtmann> eintopf: If you want to make your life a bit simpler, you or the driver maintainer can just ack patches and I apply them to bluetooth-next tree.
20:05 < holtmann> eintopf: Seriously I can just take them straight out of linux-wpan mailing list of you want. It is dead simple for me.
20:06 < holtmann> We need to get to a level where net/6lowpan/ dependencies on Bluetooth and IEEE 802.15.4 are not affecting itself that much anymore and then you can just submit directly to wireless-next
tree.
20:07 < holtmann> So if you want to focus on hacking on the code, I can take care of getting you a tree you can work in.
</qoute>
That's a very nice offer and I will accept it. Thanks.
The new behaviour:
- 802.15.4: base on bluetooth-next and send it to linux-wpan.
- Here Marcel waits for driver maintainers or me.
- 6LoWPAN GENERIC: base on bluetooth-next and send it to linux-wpan,
linux-bluetooth.
- Here Marcel waits for Jukka or me.
Hope that is okay. We need to do this until:
"We need to get to a level where net/6lowpan/ dependencies on Bluetooth and IEEE 802.15.4 are not affecting itself that much anymore"
then we can send 802.15.4 patches (hopefully pull-request, yea I will
learn that) also to wireless/wireless-next.
Hope all are fine with this solution at the moment.
- Alex
reply other threads:[~2014-10-07 7:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20141007074025.GA2768@omega \
--to=alex.aring@gmail.com \
--cc=linux-wpan@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.