From: Varka Bhadram <varkabhadram@gmail.com>
To: Alexander Aring <alex.aring@gmail.com>
Cc: linux-wpan@vger.kernel.org, linux-bluetooth@vger.kernel.org,
alan@signal11.us, Varka Bhadram <varkab@cdac.in>
Subject: Re: [PATCH bluetooth-next v2 0/3] cleanup for mrf24j40 driver
Date: Fri, 19 Sep 2014 15:01:32 +0530 [thread overview]
Message-ID: <541BF7F4.4020508@gmail.com> (raw)
In-Reply-To: <20140919090611.GA17051@omega>
Hi Alex,
On 09/19/2014 02:36 PM, Alexander Aring wrote:
> Hi Varka,
>
> nice to read you again. :-) I already thought that I was maybe a little
> bit too harsh to you for explaining changing dev->add_len during runtime
> will occur in unexcept behaviour. Sorry.
For dev->addr_len, i think David asked a question.. Isn't it..?
We need to find a way to add this. Based on this only RFC6775 is going
to work.
But i implemented RFC6775 it works for Extended addresses only. I used
the system
witch use extended address.
> Nevertheless welcome back. I want to apply it when Alan finally sends a
> "Acked-by: ...", but why is this tagged with bluetooth-next?
I am also waiting for Alan "Acked-by:..." :-)
> There are other mrf24j40 patches around and it's better to send this in
> a whole patch series when all patches are on wpan-next/testing. Then I
> will send these patches to bluetooth-next. When applied I will rebase
> the wpan-next/master to bluetooth-next/master.
Ok. I got your point. Thanks... I will respin this series with wpan-next
tag...
> Only 6LOWPAN GENERIC patches should be send to bluetooth-next.
Ok.
We are having multiple branches on wpan-next tree.
I want to know which branch is for what,..?
wpan-next/alex/wip
wpan-next/for-martin
wpan-next/for-michael
wpan-next/master
wpan-next/nhc_layer
wpan-next/tcheneau
wpan-next/testing
wpan-next/wpan_rework_rfc
--
Thanks and Regards,
Varka Bhadram.
next prev parent reply other threads:[~2014-09-19 9:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 4:45 [PATCH bluetooth-next v2 0/3] cleanup for mrf24j40 driver Varka Bhadram
2014-09-19 4:45 ` [PATCH bluetooth-next v2 1/3] mrf24j40: fix Missing a blank line after declarations Varka Bhadram
2014-09-19 4:45 ` [PATCH bluetooth-next v2 2/3] mrf24j40: remove unnecessary return statement Varka Bhadram
2014-09-19 4:45 ` [PATCH bluetooth-next v2 3/3] mrf24j40: use pr_* / dev_* instead of printk() Varka Bhadram
2014-09-19 9:06 ` [PATCH bluetooth-next v2 0/3] cleanup for mrf24j40 driver Alexander Aring
2014-09-19 9:31 ` Varka Bhadram [this message]
2014-09-19 9:41 ` Alexander Aring
2014-09-19 9:44 ` Varka Bhadram
2014-09-19 9:48 ` Alexander Aring
2014-09-19 10:26 ` Varka Bhadram
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=541BF7F4.4020508@gmail.com \
--to=varkabhadram@gmail.com \
--cc=alan@signal11.us \
--cc=alex.aring@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=varkab@cdac.in \
/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.