All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoffer Holmstedt <christoffer@christofferholmstedt.se>
To: Varka Bhadram <varkabhadram@gmail.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: [PATCH wpan-tools 0/2] Update cca mode and options output
Date: Thu, 4 Jun 2015 14:12:02 +0200	[thread overview]
Message-ID: <20150604121202.GE3045@probook-6560b> (raw)
In-Reply-To: <55703BBD.4010903@gmail.com>

On Thu, Jun 04, 2015 at 05:21:25PM +0530, Varka Bhadram wrote:
> Hi Christoffer Holmstedt,
> 
> On 06/04/2015 02:50 PM, Christoffer Holmstedt wrote:
> 
> >Earlier cca_modes and cca_opts were printed separately but these two patches
> >now prints them together so cca_opts are only printed when the specified mode
> >  is (3).
> >
> >Output for "current" mode (only one line is printed for each wpan):
> >	cca_mode: 1, energy above threshold.
> >	cca_mode: 2, carrier sense only.
> >	cca_mode: 3, carrier sense with energy above threshold (logical operator is 'and').
> >	cca_mode: 3, carrier sense with energy above threshold (logical operator is 'or').
> >	cca_mode: 3, carrier sense with energy above threshold (logical operator is unknown).
> >	cca_mode: 4, ALOHA.
> >	cca_mode: 5, UWB preamble sense based on the SHR of a frame.
> >	cca_mode: 6, UWB preamble sense based on the packet with the multiplexed preamble.
> 
> Do you think that cca_mode number is required overhear..?
> 
> What i mean is that:
> 	The cca mode number 1 indicates that its *energy above threshold*,
> So what i feel is that printing the number is required.
> 
> May be Alex has to tell its preferred or not. I think we can remove the number.
> 
...cut...
> -- 
> Varka Bhadram
> 

I was convinced before that I needed it there, but then I tried to make my
case and I ended up with the conclusion that the user don't need it. Only
scenario it is needed is when the user wants to change it and it that case the
number is listed in the capabilities section.

I will remove the number if no one objects.

-- 
Christoffer Holmstedt

  reply	other threads:[~2015-06-04 12:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04  9:20 [PATCH wpan-tools 0/2] Update cca mode and options output Christoffer Holmstedt
2015-06-04 11:02 ` Alexander Aring
2015-06-04 11:24   ` Christoffer Holmstedt
2015-06-04 11:51 ` Varka Bhadram
2015-06-04 12:12   ` Christoffer Holmstedt [this message]
2015-06-09 14:05 ` [PATCH v2 wpan-tools 0/2] Update CCA mode and CCA " christoffer
2015-06-09 14:05   ` [PATCH v2 wpan-tools 1/2] info: add cca mode descriptive text to output christoffer
2015-06-09 14:05   ` [PATCH v2 wpan-tools 2/2] info: remove old cca options capabilities output christoffer
2015-06-10 11:18 ` [PATCH v3 wpan-tools 0/3] Update CCA mode and CCA options output Christoffer Holmstedt
2015-06-10 11:18   ` [PATCH v3 wpan-tools 1/3] info: add cca mode descriptive text to output Christoffer Holmstedt
2015-06-10 12:17     ` Alexander Aring
2015-06-10 12:29       ` Christoffer Holmstedt
2015-06-10 12:39       ` [PATCH wpan-tools] nl802154: fix misspelled enum Christoffer Holmstedt
2015-06-10 12:42         ` Alexander Aring
2015-06-10 13:07       ` [PATCH v4 wpan-tools] info: update CCA mode and CCA options output Christoffer Holmstedt
2015-06-10 13:45         ` Alexander Aring
2015-06-11  6:16           ` Christoffer Holmstedt
2015-06-11  7:42             ` Alexander Aring
2015-06-11  8:13               ` Christoffer Holmstedt
2015-06-11  8:16         ` [PATCH v5 " Christoffer Holmstedt
2015-06-11 10:14         ` [PATCH v4 " Alexander Aring
2015-06-11 11:14           ` Christoffer Holmstedt
2015-06-11 12:25           ` [PATCH v6 " Christoffer Holmstedt
2015-06-11 13:28             ` Alexander Aring
2015-06-10 11:18   ` [PATCH v3 wpan-tools 2/3] info: remove old cca options capabilities output Christoffer Holmstedt
2015-06-10 11:18   ` [PATCH v3 wpan-tools 3/3] nl802154: fix misspelled enum Christoffer Holmstedt

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=20150604121202.GE3045@probook-6560b \
    --to=christoffer@christofferholmstedt.se \
    --cc=linux-wpan@vger.kernel.org \
    --cc=varkabhadram@gmail.com \
    /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.