From: Varka Bhadram <varkab@cdac.in>
To: Alexander Aring <alex.aring@gmail.com>,
Varka Bhadram <varkabhadram@gmail.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: [PATCH wpan-tools] interface: fix interface type info
Date: Thu, 04 Jun 2015 12:41:09 +0530 [thread overview]
Message-ID: <556FFA0D.604@cdac.in> (raw)
In-Reply-To: <20150604070455.GA1232@omega>
On 06/04/2015 12:34 PM, Alexander Aring wrote:
> On Wed, Jun 03, 2015 at 11:21:38AM +0530, Varka Bhadram wrote:
>> Signed-off-by: Varka Bhadram <varkab@cdac.in>
>> ---
>> src/interface.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/src/interface.c b/src/interface.c
>> index e501763..1c59876 100644
>> --- a/src/interface.c
>> +++ b/src/interface.c
>> @@ -28,7 +28,7 @@ const char *iftype_name(enum nl802154_iftype iftype)
>> case NL802154_IFTYPE_COORD:
>> return "coordinator";
>> default:
>> - sprintf(modebuf, "Unknown mode (%d)", iftype);
>> + sprintf(modebuf, "Invalid iftype (%d)", iftype);
>> return modebuf;
> This error message is like iw tool. I don't know how we strict we should
> make the behaviour like wireless here. I think it's okay to change that.
>
> But note there is also a "modebuf" and you changed "Unknown mode ..." to
> "Unknown iftype..." if you want to change it then I would assume to make
> everything to "iftypeFOOBAR". I mean change "modebuf" to "iftypebuf" or
> something else.
Yes. Agree with you. This leads to a confusion.
I will change to *iftypebuf*. V2 is on the way.
Thanks
> I can understand "Unknown mode" is confusing. But to handle now "iftypeFOO"
> and "modeFOO" is more confusing than before.
>
> - Alex
--
Varka Bhadram
-------------------------------------------------------------------------------------------------------------------------------
[ C-DAC is on Social-Media too. Kindly follow us at:
Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ]
This e-mail is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies and the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email
is strictly prohibited and appropriate legal action will be taken.
-------------------------------------------------------------------------------------------------------------------------------
prev parent reply other threads:[~2015-06-04 7:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 5:51 [PATCH wpan-tools] interface: fix interface type info Varka Bhadram
2015-06-04 7:04 ` Alexander Aring
2015-06-04 7:11 ` 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=556FFA0D.604@cdac.in \
--to=varkab@cdac.in \
--cc=alex.aring@gmail.com \
--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.