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:56:34 +0530 [thread overview]
Message-ID: <541C04DA.5030707@gmail.com> (raw)
In-Reply-To: <20140919094830.GB19085@omega>
On 09/19/2014 03:18 PM, Alexander Aring wrote:
> On Fri, Sep 19, 2014 at 03:14:11PM +0530, Varka Bhadram wrote:
>> On 09/19/2014 03:11 PM, Alexander Aring wrote:
>>> On Fri, Sep 19, 2014 at 03:01:32PM +0530, Varka Bhadram wrote:
>>>> 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..?
>>>>
>>> yes, I didn't answer. I decide now to put this issue at the last item of
>>> my todo queue. If you like you can try it. I will answer him that I do
>>> other things right now and this issue is more complex.
>>>
>>>
>>> Also you did the cc2520 driver, you can add you as maintainer for this
>>> driver. I have such devices here but on contiki nodes.
>>>
>> You mean to say that i need to add an entry in MAINTAINER file or ..?
>>
> not need, only if you like. I have no idea about the cc2520 driver.
>
> If there cames patches in, I can only look for syntax and according
> interaction with mac802154 stack.
Ya.. I can be maintainer for CC2520 driver.
I will look into the cc2520 driver patches.
Thanks
--
Regards,
Varka Bhadram.
prev parent reply other threads:[~2014-09-19 10:29 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
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 [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=541C04DA.5030707@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 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).