On Tue, Aug 04, 2015 at 08:00:09PM +0200, Alexander Aring wrote: > On Tue, Aug 04, 2015 at 06:40:46PM +0200, Stefan Schmidt wrote: > > Hello. > > > > On 30/07/15 10:55, Alexander Aring wrote: > > >This patch changes the default min value of max_frame_retries to 0 and > > >changes the max_frame_retries default value to 3 which is also 802.15.4 > > >default. > > You mean min_frame_retries to 0 here? > > No, you mixed "frame_retries" ranges with "frame_retries" value. > I need to admit, the mib value in 802.15.4 is named "max_frame_retries". But it is sounds bad to name the variables for the range to: min_max_frame_retries and max_max_frame_retries so for the range we drop the "max" here. At min_be and max_be, we need to do that, because we have a "min": min_minbe, max_minbe, min_maxbe, max_maxbe. But for "max_frame_retries" there exists no "min_frame_retries" inside the 802.15.4 mib. We have this at maxbe, minbe because it's a random generated number for some range, "max_frame_retries" is a static value. - Alex -- To unsubscribe from this list: send the line "unsubscribe linux-wpan" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
