All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: linux-wpan@vger.kernel.org
Cc: Alexander Aring <alex.aring@gmail.com>
Subject: [PATCH wpan-misc 2/2] website: add new opentask entries
Date: Fri,  1 May 2015 18:04:48 +0200	[thread overview]
Message-ID: <1430496288-17239-2-git-send-email-alex.aring@gmail.com> (raw)
In-Reply-To: <1430496288-17239-1-git-send-email-alex.aring@gmail.com>

Signed-off-by: Alexander Aring <alex.aring@gmail.com>
---
 website/index.txt | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/website/index.txt b/website/index.txt
index e6e2427..7cede5d 100644
--- a/website/index.txt
+++ b/website/index.txt
@@ -147,6 +147,8 @@ https://github.com/linux-wpan/linux-wpan-next/blob/wpan_rework_rfc/net/ieee80215
 * devicetree extended addr setting, draft is here http://www.spinics.net/lists/linux-wpan/msg01503.html[ieee802154: add usual way to get extended address via device tree]
 * RPL? - not our job, need to go through ipv6 netdev community, but we should do something to have a "started" mainline solution.
 * cleanup/fix 802.15.4 af raw/dgram socket code. We should use bluetooth socket code as example.
+* In wireless exists a "station dump", we need something similar "node dump" with all neighbour nodes and their last LQI value, addresses, etc. information.
+* A wpan-phy is an own device class, we need pm suspend handling like in wireless http://lxr.free-electrons.com/source/net/wireless/sysfs.c#L154[callbacks which are in #ifdef CONFIG_PM].
 
 Rework
 ~~~~~~
-- 
2.3.6


      reply	other threads:[~2015-05-01 16:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-01 16:04 [PATCH wpan-misc 1/2] website: remove finished opentasks Alexander Aring
2015-05-01 16:04 ` 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=1430496288-17239-2-git-send-email-alex.aring@gmail.com \
    --to=alex.aring@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    /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.