[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20111114.002202.1201536915576676890.davem@davemloft.net>
Date: Mon, 14 Nov 2011 00:22:02 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: alex.bluesman.smirnov@...il.com
Cc: dbaryshkov@...il.com, netdev@...r.kernel.org,
linux-zigbee-devel@...ts.sourceforge.net, jonsmirl@...il.com
Subject: Re: [PATCH series][6LoWPAN][net-next]
From: Alexander Smirnov <alex.bluesman.smirnov@...il.com>
Date: Thu, 10 Nov 2011 20:32:58 +0300
> Hello all,
>
> The following patch series adds both major feature and minor fixes.
> Please find detailed description in each of the patches.
>
> Just to summarize current development status:
> By using MAC and PHY layers support from
> "http://sourceforge.net/projects/linux-zigbee"
> project now it's possible to run generic network applications (ssh, iperf) over
> ieee802.15.4 network.
>
> iperf shows about ~40Kbits/sec for TCP
All applied, thanks.
In future patch submissions, please layout your Subject lines
correctly.
Everything that is inside of brackes "[]" will be removed before
the subject line is placed at the top of the commit message. So
as-is, your commits would lack any kind of indication of where
the code changes were occuring since the "6LowPAN" part was removed.
In fact, you didn't mention 6LowPAN at all in the subject line
of some of your commits. This is unacceptable. There must always
be a subject prefix of the form "${SUBSYSTEM}: " so that what
ends up in the commit message lets readers know the general area
where the change was made.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists