From: Pavel Roskin <proski@gnu.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH net-next 00/21] treewide: Use consistent api style for address testing
Date: Fri, 19 Oct 2012 11:55:17 -0400 [thread overview]
Message-ID: <20121019115517.7b8514a8@mj> (raw)
In-Reply-To: <1350630254.2293.183.camel@edumazet-glaptop>
On Fri, 19 Oct 2012 09:04:14 +0200
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> Yes they are some names discrepancies, thats a big deal.
>
> And we have alloc_skb() / kfree_skb() / skb_clone()
>
> Why not skb_alloc() / skb_free() / skb_clone() ?
>
> Some people actually know current code by name of functions, they dont
> want to change their mind and having to grep include files and git log
> to learn the new names of an old function, especially when traveling
> and using a laptop.
I agree.
Also, it makes sense to introduce a more consistent name for a function
when it's improved in some way and the callers need to be adjusted or
re-checked.
That way, the old name can be phased out as the code is made compatible
with the new function.
--
Regards,
Pavel Roskin
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Roskin <proski@gnu.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: linux-mips@linux-mips.org, b.a.t.m.a.n@lists.open-mesh.org,
linux-doc@vger.kernel.org, brcm80211-dev-list@broadcom.com,
users@rt2x00.serialmonkey.com, linux-sctp@vger.kernel.org,
devel@open-fcoe.org, dev@openvswitch.org,
linux-s390@vger.kernel.org, wimax@linuxwimax.org,
linux-scsi@vger.kernel.org, linux-rdma@vger.kernel.org,
bridge@lists.linux-foundation.org, lvs-devel@vger.kernel.org,
coreteam@netfilter.org, b43-dev@lists.infradead.org,
cbe-oss-dev@lists.ozlabs.org, devel@driverdev.osuosl.org,
user-mode-linux-devel@lists.sourceforge.net,
devicetree-discuss@lists.ozlabs.org,
davinci-linux-open-source@linux.davincidsp.com,
netfilter@vger.kernel.org,
user-mode-linux-user@lists.sourceforge.net,
linux-arm-kernel@lists.infradead.org, linux-nfs@vger.kernel.org,
linux-parisc@vger.kernel.org, netdev@vger.kernel.org,
linux-usb@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org, e1000-devel@lists.sourceforge.net,
ath9k-devel@lists.ath9k.org, netfilter-devel@vger.kernel.org,
Joe Perches <joe@perches.com>,
uclinux-dist-devel@blackfin.uclinux.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [B.A.T.M.A.N.] [ath9k-devel] [PATCH net-next 00/21] treewide: Use consistent api style for address testing
Date: Fri, 19 Oct 2012 11:55:17 -0400 [thread overview]
Message-ID: <20121019115517.7b8514a8@mj> (raw)
In-Reply-To: <1350630254.2293.183.camel@edumazet-glaptop>
On Fri, 19 Oct 2012 09:04:14 +0200
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> Yes they are some names discrepancies, thats a big deal.
>
> And we have alloc_skb() / kfree_skb() / skb_clone()
>
> Why not skb_alloc() / skb_free() / skb_clone() ?
>
> Some people actually know current code by name of functions, they dont
> want to change their mind and having to grep include files and git log
> to learn the new names of an old function, especially when traveling
> and using a laptop.
I agree.
Also, it makes sense to introduce a more consistent name for a function
when it's improved in some way and the callers need to be adjusted or
re-checked.
That way, the old name can be phased out as the code is made compatible
with the new function.
--
Regards,
Pavel Roskin
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Roskin <proski@gnu.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: linux-mips@linux-mips.org, b.a.t.m.a.n@lists.open-mesh.org,
linux-doc@vger.kernel.org, brcm80211-dev-list@broadcom.com,
users@rt2x00.serialmonkey.com, linux-sctp@vger.kernel.org,
devel@open-fcoe.org, dev@openvswitch.org,
linux-s390@vger.kernel.org, wimax@linuxwimax.org,
linux-scsi@vger.kernel.org, linux-rdma@vger.kernel.org,
bridge@lists.linux-foundation.org, lvs-devel@vger.kernel.org,
coreteam@netfilter.org, b43-dev@lists.infradead.org,
cbe-oss-dev@lists.ozlabs.org, devel@driverdev.osuosl.org,
user-mode-linux-devel@lists.sourceforge.net,
devicetree-discuss@lists.ozlabs.org,
davinci-linux-open-source@linux.davincidsp.com,
netfilter@vger.kernel.org,
user-mode-linux-user@lists.sourceforge.net,
linux-arm-kernel@lists.infradead.org, linux-nfs@vger.kernel.org,
linux-parisc@vger.kernel.org, netdev@vger.kernel.org,
linux-usb@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org, e1000-devel@lists.sourceforge.net,
ath9k-devel@lists.ath9k.org, netfilter-devel@vger.kernel.org,
Joe Perches <joe@perches.com>,
uclinux-dist-devel@blackfin.uclinux.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [Bridge] [ath9k-devel] [PATCH net-next 00/21] treewide: Use consistent api style for address testing
Date: Fri, 19 Oct 2012 11:55:17 -0400 [thread overview]
Message-ID: <20121019115517.7b8514a8@mj> (raw)
In-Reply-To: <1350630254.2293.183.camel@edumazet-glaptop>
On Fri, 19 Oct 2012 09:04:14 +0200
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> Yes they are some names discrepancies, thats a big deal.
>
> And we have alloc_skb() / kfree_skb() / skb_clone()
>
> Why not skb_alloc() / skb_free() / skb_clone() ?
>
> Some people actually know current code by name of functions, they dont
> want to change their mind and having to grep include files and git log
> to learn the new names of an old function, especially when traveling
> and using a laptop.
I agree.
Also, it makes sense to introduce a more consistent name for a function
when it's improved in some way and the callers need to be adjusted or
re-checked.
That way, the old name can be phased out as the code is made compatible
with the new function.
--
Regards,
Pavel Roskin
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Roskin <proski@gnu.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Joe Perches <joe@perches.com>,
linux-mips@linux-mips.org, linux-usb@vger.kernel.org,
linux-doc@vger.kernel.org, brcm80211-dev-list@broadcom.com,
linux-kernel@vger.kernel.org, linux-sctp@vger.kernel.org,
devel@open-fcoe.org, dev@openvswitch.org,
linux-s390@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net,
linux-scsi@vger.kernel.org, linux-rdma@vger.kernel.org,
bridge@lists.linux-foundation.org, lvs-devel@vger.kernel.org,
coreteam@netfilter.org, b43-dev@lists.infradead.org,
cbe-oss-dev@lists.ozlabs.org, devel@driverdev.osuosl.org,
wimax@linuxwimax.org, devicetree-discuss@lists.ozlabs.org,
linux-nfs@vger.kernel.org, netfilter@vger.kernel.org,
user-mode-linux-user@lists.sourceforge.net,
linux-arm-kernel@lists.infradead.org,
davinci-linux-open-source@linux.davincidsp.com,
linux-parisc@vger.kernel.org, netdev@vger.kernel.org,
b.a.t.m.a.n@lists.open-mesh.org, linux-wireless@vger.kernel.org,
users@rt2x00.serialmonkey.com, e1000-devel@lists.sourceforge.net,
ath9k-devel@lists.ath9k.org, netfilter-devel@vger.kernel.org,
uclinux-dist-devel@blackfin.uclinux.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [ath9k-devel] [PATCH net-next 00/21] treewide: Use consistent api style for address testing
Date: Fri, 19 Oct 2012 11:55:17 -0400 [thread overview]
Message-ID: <20121019115517.7b8514a8@mj> (raw)
In-Reply-To: <1350630254.2293.183.camel@edumazet-glaptop>
On Fri, 19 Oct 2012 09:04:14 +0200
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> Yes they are some names discrepancies, thats a big deal.
>
> And we have alloc_skb() / kfree_skb() / skb_clone()
>
> Why not skb_alloc() / skb_free() / skb_clone() ?
>
> Some people actually know current code by name of functions, they dont
> want to change their mind and having to grep include files and git log
> to learn the new names of an old function, especially when traveling
> and using a laptop.
I agree.
Also, it makes sense to introduce a more consistent name for a function
when it's improved in some way and the callers need to be adjusted or
re-checked.
That way, the old name can be phased out as the code is made compatible
with the new function.
--
Regards,
Pavel Roskin
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Roskin <proski-mXXj517/zsQ@public.gmane.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: linux-mips-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org,
b.a.t.m.a.n-ZwoEplunGu2X36UT3dwllkB+6BGkLq7r@public.gmane.org,
linux-doc@vger.kernel.org,
brcm80211-dev-list-dY08KVG/lbpWk0Htik3J/w@public.gmane.org,
users-poMEt7QlJxcwIE2E9O76wjtx2kNaKg5H@public.gmane.org,
linux-sctp@vger.kernel.org,
devel-s9riP+hp16TNLxjTenLetw@public.gmane.org,
dev@openvswitch.org, linux-s390@vger.kernel.org,
wimax-BPSAo7wm5JOHVYUYWc+uSQ@public.gmane.org,
linux-scsi@vger.kernel.org, linux-rdma@vger.kernel.org,
bridge@lists.linux-foundation.org, lvs-devel@vger.kernel.org,
coreteam@netfilter.org, b43-dev@lists.infradead.org,
cbe-oss-dev@lists.ozlabs.org, devel@driverdev.osuosl.org,
user-mode-linux-devel@lists.sourceforge.net,
devicetree-discuss@lists.ozlabs.org,
davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org,
netfilter@vger.kernel.org,
user-mode-linux-user@lists.sourceforge.net,
linux-arm-kernel@lists.infradead.org, linux-nfs@vger.kernel.org,
linux-parisc@vger.kernel.org, netdev@vger.kernel.org,
linux-usb@vger.kernel.org, linux-wireless@vger.kernel.org, l
Subject: Re: [ath9k-devel] [PATCH net-next 00/21] treewide: Use consistent api style for address testing
Date: Fri, 19 Oct 2012 11:55:17 -0400 [thread overview]
Message-ID: <20121019115517.7b8514a8@mj> (raw)
In-Reply-To: <1350630254.2293.183.camel@edumazet-glaptop>
On Fri, 19 Oct 2012 09:04:14 +0200
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> Yes they are some names discrepancies, thats a big deal.
>
> And we have alloc_skb() / kfree_skb() / skb_clone()
>
> Why not skb_alloc() / skb_free() / skb_clone() ?
>
> Some people actually know current code by name of functions, they dont
> want to change their mind and having to grep include files and git log
> to learn the new names of an old function, especially when traveling
> and using a laptop.
I agree.
Also, it makes sense to introduce a more consistent name for a function
when it's improved in some way and the callers need to be adjusted or
re-checked.
That way, the old name can be phased out as the code is made compatible
with the new function.
--
Regards,
Pavel Roskin
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Roskin <proski-mXXj517/zsQ@public.gmane.org>
To: Eric Dumazet <eric.dumazet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-mips-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org,
b.a.t.m.a.n-ZwoEplunGu2X36UT3dwllkB+6BGkLq7r@public.gmane.org,
linux-doc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
brcm80211-dev-list-dY08KVG/lbpWk0Htik3J/w@public.gmane.org,
users-poMEt7QlJxcwIE2E9O76wjtx2kNaKg5H@public.gmane.org,
linux-sctp-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devel-s9riP+hp16TNLxjTenLetw@public.gmane.org,
dev-yBygre7rU0TnMu66kgdUjQ@public.gmane.org,
linux-s390-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
wimax-BPSAo7wm5JOHVYUYWc+uSQ@public.gmane.org,
linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
bridge-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
lvs-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
coreteam-Cap9r6Oaw4JrovVCs/uTlw@public.gmane.org,
b43-dev-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
cbe-oss-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
devel-gWbeCf7V1WCQmaza687I9mD2FQJk+8+b@public.gmane.org,
user-mode-linux-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org,
netfilter-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
user-mode-linux-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-parisc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, l
Subject: Re: [ath9k-devel] [PATCH net-next 00/21] treewide: Use consistent api style for address testing
Date: Fri, 19 Oct 2012 11:55:17 -0400 [thread overview]
Message-ID: <20121019115517.7b8514a8@mj> (raw)
In-Reply-To: <1350630254.2293.183.camel@edumazet-glaptop>
On Fri, 19 Oct 2012 09:04:14 +0200
Eric Dumazet <eric.dumazet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Yes they are some names discrepancies, thats a big deal.
>
> And we have alloc_skb() / kfree_skb() / skb_clone()
>
> Why not skb_alloc() / skb_free() / skb_clone() ?
>
> Some people actually know current code by name of functions, they dont
> want to change their mind and having to grep include files and git log
> to learn the new names of an old function, especially when traveling
> and using a laptop.
I agree.
Also, it makes sense to introduce a more consistent name for a function
when it's improved in some way and the callers need to be adjusted or
re-checked.
That way, the old name can be phased out as the code is made compatible
with the new function.
--
Regards,
Pavel Roskin
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Roskin <proski-mXXj517/zsQ@public.gmane.org>
To: Eric Dumazet <eric.dumazet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-mips-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org,
b.a.t.m.a.n-ZwoEplunGu2X36UT3dwllkB+6BGkLq7r@public.gmane.org,
linux-doc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
brcm80211-dev-list-dY08KVG/lbpWk0Htik3J/w@public.gmane.org,
users-poMEt7QlJxcwIE2E9O76wjtx2kNaKg5H@public.gmane.org,
linux-sctp-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devel-s9riP+hp16TNLxjTenLetw@public.gmane.org,
dev-yBygre7rU0TnMu66kgdUjQ@public.gmane.org,
linux-s390-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
wimax-BPSAo7wm5JOHVYUYWc+uSQ@public.gmane.org,
linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
bridge-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
lvs-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
coreteam-Cap9r6Oaw4JrovVCs/uTlw@public.gmane.org,
b43-dev-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
cbe-oss-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
devel-gWbeCf7V1WCQmaza687I9mD2FQJk+8+b@public.gmane.org,
user-mode-linux-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org,
netfilter-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
user-mode-linux-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-parisc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.orgl
Subject: Re: [ath9k-devel] [PATCH net-next 00/21] treewide: Use consistent api style for address testing
Date: Fri, 19 Oct 2012 11:55:17 -0400 [thread overview]
Message-ID: <20121019115517.7b8514a8@mj> (raw)
In-Reply-To: <1350630254.2293.183.camel@edumazet-glaptop>
On Fri, 19 Oct 2012 09:04:14 +0200
Eric Dumazet <eric.dumazet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Yes they are some names discrepancies, thats a big deal.
>
> And we have alloc_skb() / kfree_skb() / skb_clone()
>
> Why not skb_alloc() / skb_free() / skb_clone() ?
>
> Some people actually know current code by name of functions, they dont
> want to change their mind and having to grep include files and git log
> to learn the new names of an old function, especially when traveling
> and using a laptop.
I agree.
Also, it makes sense to introduce a more consistent name for a function
when it's improved in some way and the callers need to be adjusted or
re-checked.
That way, the old name can be phased out as the code is made compatible
with the new function.
--
Regards,
Pavel Roskin
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Roskin <proski@gnu.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: linux-mips@linux-mips.org, b.a.t.m.a.n@lists.open-mesh.org,
linux-doc@vger.kernel.org, brcm80211-dev-list@broadcom.com,
users@rt2x00.serialmonkey.com, linux-sctp@vger.kernel.org,
devel@open-fcoe.org, dev@openvswitch.org,
linux-s390@vger.kernel.org, wimax@linuxwimax.org,
linux-scsi@vger.kernel.org, linux-rdma@vger.kernel.org,
bridge@lists.linux-foundation.org, lvs-devel@vger.kernel.org,
coreteam@netfilter.org, b43-dev@lists.infradead.org,
cbe-oss-dev@lists.ozlabs.org, devel@driverdev.osuosl.org,
user-mode-linux-devel@lists.sourceforge.net,
devicetree-discuss@lists.ozlabs.org,
davinci-linux-open-source@linux.davincidsp.com,
netfilter@vger.kernel.org,
user-mode-linux-user@lists.sourceforge.net,
linux-arm-kernel@lists.infradead.org, linux-nfs@vger.kernel.org,
linux-parisc@vger.kernel.org, netdev@vger.kernel.org,
linux-usb@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org, e1000-devel@lists.sourceforge.net,
ath9k-devel@lists.ath9k.org, netfilter-devel@vger.kernel.org,
Joe Perches <joe@perches.com>,
uclinux-dist-devel@blackfin.uclinux.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [ath9k-devel] [PATCH net-next 00/21] treewide: Use consistent api style for address testing
Date: Fri, 19 Oct 2012 11:55:17 -0400 [thread overview]
Message-ID: <20121019115517.7b8514a8@mj> (raw)
In-Reply-To: <1350630254.2293.183.camel@edumazet-glaptop>
On Fri, 19 Oct 2012 09:04:14 +0200
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> Yes they are some names discrepancies, thats a big deal.
>
> And we have alloc_skb() / kfree_skb() / skb_clone()
>
> Why not skb_alloc() / skb_free() / skb_clone() ?
>
> Some people actually know current code by name of functions, they dont
> want to change their mind and having to grep include files and git log
> to learn the new names of an old function, especially when traveling
> and using a laptop.
I agree.
Also, it makes sense to introduce a more consistent name for a function
when it's improved in some way and the callers need to be adjusted or
re-checked.
That way, the old name can be phased out as the code is made compatible
with the new function.
--
Regards,
Pavel Roskin
WARNING: multiple messages have this Message-ID (diff)
From: proski@gnu.org (Pavel Roskin)
To: linux-arm-kernel@lists.infradead.org
Subject: [ath9k-devel] [PATCH net-next 00/21] treewide: Use consistent api style for address testing
Date: Fri, 19 Oct 2012 11:55:17 -0400 [thread overview]
Message-ID: <20121019115517.7b8514a8@mj> (raw)
In-Reply-To: <1350630254.2293.183.camel@edumazet-glaptop>
On Fri, 19 Oct 2012 09:04:14 +0200
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> Yes they are some names discrepancies, thats a big deal.
>
> And we have alloc_skb() / kfree_skb() / skb_clone()
>
> Why not skb_alloc() / skb_free() / skb_clone() ?
>
> Some people actually know current code by name of functions, they dont
> want to change their mind and having to grep include files and git log
> to learn the new names of an old function, especially when traveling
> and using a laptop.
I agree.
Also, it makes sense to introduce a more consistent name for a function
when it's improved in some way and the callers need to be adjusted or
re-checked.
That way, the old name can be phased out as the code is made compatible
with the new function.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2012-10-19 15:55 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 3:55 [ath9k-devel] [PATCH net-next 00/21] treewide: Use consistent api style for address testing Joe Perches
2012-10-19 3:55 ` Joe Perches
2012-10-19 3:55 ` Joe Perches
2012-10-19 3:55 ` Joe Perches
2012-10-19 3:55 ` Joe Perches
2012-10-19 3:55 ` Joe Perches
2012-10-19 3:55 ` Joe Perches
2012-10-19 3:55 ` [Bridge] " Joe Perches
2012-10-19 3:55 ` [B.A.T.M.A.N.] " Joe Perches
2012-10-19 3:55 ` [PATCH net-next 01/21] etherdevice: Rename is_<foo>_ether_addr tests to eth_addr_<foo> Joe Perches
2012-10-19 3:55 ` [B.A.T.M.A.N.] [PATCH net-next 02/21] net: Convert is_<foo>_ether_addr uses " Joe Perches
2012-10-19 3:55 ` Joe Perches
2012-10-19 3:55 ` Joe Perches
2012-10-19 3:55 ` [Bridge] " Joe Perches
2012-10-19 3:55 ` [PATCH net-next 03/21] arch: " Joe Perches
2012-10-19 3:55 ` Joe Perches
2012-10-19 3:55 ` [ath9k-devel] [PATCH net-next 04/21] wireless: " Joe Perches
2012-10-19 3:55 ` Joe Perches
2012-10-19 3:55 ` Joe Perches
2012-10-19 3:55 ` Joe Perches
2012-10-20 2:30 ` [ath9k-devel] " Bing Zhao
2012-10-20 2:30 ` Bing Zhao
2012-10-20 2:30 ` Bing Zhao
2012-10-20 10:51 ` [ath9k-devel] " Luciano Coelho
2012-10-20 10:51 ` Luciano Coelho
2012-10-20 16:19 ` Arend van Spriel
2012-10-19 4:13 ` [PATCH net-next 03/21] arch: " Joe Perches
2012-10-19 4:14 ` [PATCH net-next 05/21] drivers: net: " Joe Perches
2012-10-19 4:14 ` [PATCH net-next 06/21] staging: " Joe Perches
2012-10-19 4:14 ` [PATCH net-next 07/21] infiniband: " Joe Perches
2012-10-19 4:14 ` [PATCH net-next 08/21] scsi: " Joe Perches
2012-10-19 4:14 ` [PATCH net-next 09/21] of: " Joe Perches
2012-10-19 4:14 ` [PATCH net-next 10/21] s390: " Joe Perches
2012-10-19 4:14 ` [PATCH net-next 11/21] usb: " Joe Perches
2012-10-19 4:14 ` [PATCH net-next 12/21] uwb: " Joe Perches
2012-10-19 4:14 ` [PATCH net-next 13/21] Documentation: networking: " Joe Perches
2012-10-19 4:14 ` [PATCH net-next 14/21] llc_if.h: " Joe Perches
2012-10-19 4:14 ` [PATCH net-next 15/21] in.h: Rename ipv4_is_<foo> functions to ipv4_addr_<foo> Joe Perches
2012-10-19 4:15 ` [PATCH net-next 16/21] net: Convert ipv4_is_<foo> uses " Joe Perches
2012-10-19 4:15 ` [PATCH net-next 17/21] infiniband: " Joe Perches
2012-10-19 4:15 ` [PATCH net-next 18/21] ath6kl: " Joe Perches
2012-10-19 4:15 ` [PATCH net-next 19/21] parisc: " Joe Perches
2012-10-19 4:15 ` [PATCH net-next 20/21] lockd: " Joe Perches
2012-10-19 4:15 ` [PATCH net-next 21/21] sctp: " Joe Perches
2012-10-19 7:04 ` [ath9k-devel] [PATCH net-next 00/21] treewide: Use consistent api style for address testing Eric Dumazet
2012-10-19 7:04 ` Eric Dumazet
2012-10-19 7:04 ` Eric Dumazet
2012-10-19 7:04 ` Eric Dumazet
2012-10-19 7:04 ` Eric Dumazet
2012-10-19 7:04 ` Eric Dumazet
2012-10-19 7:04 ` Eric Dumazet
2012-10-19 7:04 ` [Bridge] " Eric Dumazet
2012-10-19 7:04 ` [B.A.T.M.A.N.] " Eric Dumazet
2012-10-19 10:29 ` Joe Perches
2012-10-19 15:55 ` Pavel Roskin [this message]
2012-10-19 15:55 ` [ath9k-devel] " Pavel Roskin
2012-10-19 15:55 ` Pavel Roskin
2012-10-19 15:55 ` Pavel Roskin
2012-10-19 15:55 ` Pavel Roskin
2012-10-19 15:55 ` Pavel Roskin
2012-10-19 15:55 ` Pavel Roskin
2012-10-19 15:55 ` [Bridge] " Pavel Roskin
2012-10-19 15:55 ` [B.A.T.M.A.N.] " Pavel Roskin
2012-10-19 16:39 ` Joe Perches
2012-10-19 16:39 ` Joe Perches
2012-10-19 16:39 ` Joe Perches
2012-10-19 7:36 ` David Miller
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=20121019115517.7b8514a8@mj \
--to=proski@gnu.org \
--cc=ath9k-devel@lists.ath9k.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.