diff mbox

[3/3] documentation: fix wrt. headers rename

Message ID 1249457297-8355-4-git-send-email-dbaryshkov@gmail.com
State Not Applicable, archived
Delegated to: David Miller
Headers show

Commit Message

Dmitry Baryshkov Aug. 5, 2009, 7:28 a.m. UTC
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
---
 Documentation/networking/ieee802154.txt |    9 ++++-----
 1 files changed, 4 insertions(+), 5 deletions(-)

Comments

David Miller Aug. 6, 2009, 3:22 a.m. UTC | #1
From: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Date: Wed,  5 Aug 2009 11:28:17 +0400

> Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>

What are you generating these patches against?

> @@ -72,5 +72,4 @@ SoftMAC
>  We are going to provide intermediate layer implementing IEEE 802.15.4 MAC
>  in software. This is currently WIP.
>  
> -See header include/net/ieee802154/mac802154.h and several drivers in
> -drivers/ieee802154/
> +See header include/net/mac802154.h and several drivers in drivers/ieee802154/.

In net-2.6, and in Linus's tree as well, that first sentence quoted has
a typo, "implementing" is misspelled, but in whatever you're patching
against the misspelling is fixed.

Looking at your pull request:

--------------------
The following changes since commit db71789c01ae7b641f83c5aa64e7df25122f4b28:
  David S. Miller (1):
        xfrm6: Fix xfrm6_policy.c build when SYSCTL disabled.
--------------------

You're submitting these for net-next-2.6?  Didn't we just go back and
forth about trimming this patch series down to only pure bug fixes so
that they could go into net-2.6?  Given that, why are you generating
this stuff against net-next-2.6?

I'm tossing this entire series again, this is beyond frustrating.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Dmitry Baryshkov Aug. 6, 2009, 9:26 a.m. UTC | #2
On Wed, Aug 05, 2009 at 08:22:26PM -0700, David Miller wrote:
> From: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
> Date: Wed,  5 Aug 2009 11:28:17 +0400
> 
> > Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
> 
> What are you generating these patches against?
> 
> > @@ -72,5 +72,4 @@ SoftMAC
> >  We are going to provide intermediate layer implementing IEEE 802.15.4 MAC
> >  in software. This is currently WIP.
> >  
> > -See header include/net/ieee802154/mac802154.h and several drivers in
> > -drivers/ieee802154/
> > +See header include/net/mac802154.h and several drivers in drivers/ieee802154/.
> 
> In net-2.6, and in Linus's tree as well, that first sentence quoted has
> a typo, "implementing" is misspelled, but in whatever you're patching
> against the misspelling is fixed.
> 
> Looking at your pull request:
> 
> --------------------
> The following changes since commit db71789c01ae7b641f83c5aa64e7df25122f4b28:
>   David S. Miller (1):
>         xfrm6: Fix xfrm6_policy.c build when SYSCTL disabled.
> --------------------
> 
> You're submitting these for net-next-2.6?  Didn't we just go back and
> forth about trimming this patch series down to only pure bug fixes so
> that they could go into net-2.6?  Given that, why are you generating
> this stuff against net-next-2.6?

Damn. It seems I missed the difference between net-next-2.6 and net-2.6.

BTW: how should I differentiate my poll requests for net-next-2.6 and
for net-2.6 ?
David Miller Aug. 6, 2009, 5:34 p.m. UTC | #3
From: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Date: Thu, 6 Aug 2009 13:26:17 +0400

> BTW: how should I differentiate my poll requests for net-next-2.6 and
> for net-2.6 ?

Like the rest of the world by indicating the target tree in your
subject lines.  As long as it's in those initial [] brackets,
the automated GIT tools strip it all out when applying patches.

Don't you see other patch posters putting things like "[NEXT ...]" and
"[net-2.6 ...]" and "[net-next-2.6 ...]" in their subjects?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
diff mbox

Patch

diff --git a/Documentation/networking/ieee802154.txt b/Documentation/networking/ieee802154.txt
index 1d4ed66..1c0c82c 100644
--- a/Documentation/networking/ieee802154.txt
+++ b/Documentation/networking/ieee802154.txt
@@ -22,7 +22,7 @@  int sd = socket(PF_IEEE802154, SOCK_DGRAM, 0);
 .....
 
 The address family, socket addresses etc. are defined in the
-include/net/ieee802154/af_ieee802154.h header or in the special header
+include/net/af_ieee802154.h header or in the special header
 in our userspace package (see either linux-zigbee sourceforge download page
 or git tree at git://linux-zigbee.git.sourceforge.net/gitroot/linux-zigbee).
 
@@ -33,7 +33,7 @@  MLME - MAC Level Management
 ============================
 
 Most of IEEE 802.15.4 MLME interfaces are directly mapped on netlink commands.
-See the include/net/ieee802154/nl802154.h header. Our userspace tools package
+See the include/net/nl802154.h header. Our userspace tools package
 (see above) provides CLI configuration utility for radio interfaces and simple
 coordinator for IEEE 802.15.4 networks as an example users of MLME protocol.
 
@@ -54,7 +54,7 @@  Those types of devices require different approach to be hooked into Linux kernel
 HardMAC
 =======
 
-See the header include/net/ieee802154/netdevice.h. You have to implement Linux
+See the header include/net/ieee802154_netdev.h. You have to implement Linux
 net_device, with .type = ARPHRD_IEEE802154. Data is exchanged with socket family
 code via plain sk_buffs. The control block of sk_buffs will contain additional
 info as described in the struct ieee802154_mac_cb.
@@ -72,5 +72,4 @@  SoftMAC
 We are going to provide intermediate layer implementing IEEE 802.15.4 MAC
 in software. This is currently WIP.
 
-See header include/net/ieee802154/mac802154.h and several drivers in
-drivers/ieee802154/
+See header include/net/mac802154.h and several drivers in drivers/ieee802154/.