From: Stefan Schmidt <stefan@osg.samsung.com>
To: Alexander Aring <alex.aring@gmail.com>
Cc: linux-wpan@vger.kernel.org, marcel@holtmann.org
Subject: Re: [PATCH bluetooth-next 0/2] ieee802154: multiple lowpan interface support and fix mac setting
Date: Fri, 24 Jul 2015 18:29:35 +0200 [thread overview]
Message-ID: <55B267EF.8030908@osg.samsung.com> (raw)
In-Reply-To: <20150724150945.GA6594@omega>
Hello.
On 24/07/15 17:10, Alexander Aring wrote:
> On Fri, Jul 24, 2015 at 05:01:22PM +0200, Stefan Schmidt wrote:
>> Hello.
>>
>> On 24/07/15 15:01, Alexander Aring wrote:
>>> Hi,
>>>
>>> this patch series contains two patches. At first we remove the multiple
>>> lowpan interface support. I don't see any use case for that, if somebody
>>> has an use case for it. Please report your use case.
>> I had to read the commit message to find out that you mean multiple lowpan
>> interfaces on one wpan interface here. And not multiple lowpan interface on
>> one machine which I thought first. :)
>>
> ok, I will remember that. I should say more detailed information, but
> yes it's multiple lowpan interface per wpan interface.
>
> I think the reason why we have it is that some parts of the code is
> grabbed from the eth bridge rtnl code. And multiple bridges for one
> ethernet interface makes sense.
>
> In our case, we don't have any use case, I see no sense to have multiple
> lowpan interface.
>
>> The later has for sure enough use cases :)
>>
>> I don't have a use case for the former (the one you remove here) either.
>> Still we might want to consider this as an RFC here to give folks a moment
>> to speak up with they use this.
>>
> ok. Keeping this functionaltiy makes things much complicated to deal
> with it and I don't know that somebody use this functionaltiy which
> makes for me no sense. I thought already 2 years long about to remove
> this functionaltiy. :-)
Sure, fair enough. I'm not saying we have to keep it just that we might
one a bit longer than the usual patch-on-list-to-apply cycle to give
people time to speak up.
I don't have a use case for it either right now but maybe we just miss
something.
regards
Stefan Schmidt
prev parent reply other threads:[~2015-07-24 16:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 13:01 [PATCH bluetooth-next 0/2] ieee802154: multiple lowpan interface support and fix mac setting Alexander Aring
2015-07-24 13:01 ` [PATCH bluetooth-next 1/2] ieee802154: 6lowpan: remove multiple lowpan support Alexander Aring
2015-07-30 16:15 ` Stefan Schmidt
2015-07-30 22:53 ` Alexander Aring
2015-07-24 13:01 ` [PATCH bluetooth-next 2/2] mac802154: fix wpan mac setting while lowpan Alexander Aring
2015-07-30 16:17 ` Stefan Schmidt
2015-07-30 22:52 ` Alexander Aring
2015-07-31 8:54 ` Stefan Schmidt
2015-07-24 15:01 ` [PATCH bluetooth-next 0/2] ieee802154: multiple lowpan interface support and fix mac setting Stefan Schmidt
2015-07-24 15:10 ` Alexander Aring
2015-07-24 16:29 ` Stefan Schmidt [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=55B267EF.8030908@osg.samsung.com \
--to=stefan@osg.samsung.com \
--cc=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=marcel@holtmann.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