Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: linux-wpan@vger.kernel.org
Cc: kernel@pengutronix.de, mkl@pengutronix.de
Subject: Re: [RFC bluetooth-next 2/2] at86rf230: add support for dt or pdata extended addr
Date: Mon, 9 Mar 2015 10:39:34 +0100	[thread overview]
Message-ID: <20150309093933.GC711@omega> (raw)
In-Reply-To: <20150309093637.GB711@omega>

> Or should I define it driver specific. When setting "extended-addr" via
> the dt property "extended-addr" then because the driver doesn't support
> the handling.

s/dt property "extended-addr"/dt property "extended-addr" doesn't work/

sorry, I hope now it's clear what I meant here.

- Alex

      reply	other threads:[~2015-03-09  9:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-08  8:17 [RFC bluetooth-next 0/2] ieee802154: add usual way to get extended address via device tree Alexander Aring
2015-03-08  8:17 ` [RFC bluetooth-next 1/2] of: net: add support for extended address Alexander Aring
2015-03-09  9:33   ` Alexander Aring
2015-03-08  8:17 ` [RFC bluetooth-next 2/2] at86rf230: add support for dt or pdata extended addr Alexander Aring
2015-03-09  9:36   ` Alexander Aring
2015-03-09  9:39     ` Alexander Aring [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=20150309093933.GC711@omega \
    --to=alex.aring@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-wpan@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    /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