All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Varka Bhadram <varkabhadram@gmail.com>
Cc: Phoebe Buckheister <phoebe.buckheister@itwm.fraunhofer.de>,
	linux-wpan@vger.kernel.org, kernel@pengutronix.de,
	mkl@pengutronix.de
Subject: Re: [PATCHv3 bluetooth-next 2/4] nl802154: add set interface cmd
Date: Tue, 7 Apr 2015 15:14:18 +0200	[thread overview]
Message-ID: <20150407131413.GC16415@omega> (raw)
In-Reply-To: <5523CD93.6090102@gmail.com>

Hi Varka,

On Tue, Apr 07, 2015 at 05:59:07PM +0530, Varka Bhadram wrote:
> On 04/07/2015 05:51 PM, Alexander Aring wrote:
...
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-wpan" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> Instead of this its better to leave the current behavior as it is.
> 
> Why do we need to complicate the process...?

I think more this is easier for userspace application which need to call
one CMD_SET for dev or phy only, but yes... it's much complicated to
handle error handling then. The most error codes would be -EINVAL and
-ENOTSUPP and we should forget some error codes which comming from
spi_sync/spi_async calls, these are very unlikely.

To handle the -EINVAL and -ENOTSUPP error we need more stuff to check if
the phy supports that value. I will try to introduce at first such
behaviour, then we can reconsider if we need something like that or not.

- Alex

  reply	other threads:[~2015-04-07 13:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-07 11:49 [PATCHv3 bluetooth-next 0/4] ieee802154: nl802154 SET commands and pib defaults Alexander Aring
2015-04-07 11:49 ` [PATCHv3 bluetooth-next 1/4] nl802154: add set wpan phy cmd Alexander Aring
2015-04-07 11:49 ` [PATCHv3 bluetooth-next 2/4] nl802154: add set interface cmd Alexander Aring
2015-04-07 11:59   ` Phoebe Buckheister
2015-04-07 12:21     ` Alexander Aring
2015-04-07 12:29       ` Varka Bhadram
2015-04-07 13:14         ` Alexander Aring [this message]
2015-04-07 12:29       ` Phoebe Buckheister
2015-04-07 12:59         ` Alexander Aring
2015-04-07 13:02           ` Phoebe Buckheister
2015-04-07 13:25             ` Alexander Aring
2015-04-07 13:32               ` Phoebe Buckheister
2015-04-07 13:40                 ` Alexander Aring
2015-04-07 11:49 ` [PATCHv3 bluetooth-next 3/4] ieee802154: move mac pib defaults Alexander Aring
2015-04-07 11:49 ` [PATCHv3 bluetooth-next 4/4] ieee802154: set aret handling according to 802.15.4 Alexander Aring

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=20150407131413.GC16415@omega \
    --to=alex.aring@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-wpan@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=phoebe.buckheister@itwm.fraunhofer.de \
    --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.