From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: "Matthias Kaehlcke" <matthias.kaehlcke@gmail.com>,
developers@islsm.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH 2/2] use list_for_each_entry() for iteration in Prism 54 driver
Date: Tue, 29 May 2007 11:38:05 -0400 [thread overview]
Message-ID: <43e72e890705290838o50fd0897re3f8fc7547b3758e@mail.gmail.com> (raw)
In-Reply-To: <20070527103951.GK31790@traven>
On 5/27/07, Matthias Kaehlcke <matthias.kaehlcke@gmail.com> wrote:
> El Fri, May 25, 2007 at 03:04:44PM +0200 Matthias Kaehlcke ha dit:
>
> > Use list_for_each() in the Prism54 driver to iterate over the MAC list
>
> In response to a similar patch Christoph Hellwig suggests the use of
> list_for_each_entry() instead of list_for_each(). Here is a evolution
> of the patch that takes into account Christophs' suggestion
>
> --
>
> Prism54 driver: Use list_for_each_entry() instead of manual iteration
> and substitute a list_for_each_safe() loop with
> list_for_each_entry_safe()
>
> Signed-off-by: Matthias Kaehlcke <matthias.kaehlcke@gmail.com>
Singed-off-by: Luis R. Rodriguez <mcgrof@gmail.com>
Looks good,
Luis
> --
>
> diff --git a/drivers/net/wireless/prism54/isl_ioctl.c b/drivers/net/wireless/prism54/isl_ioctl.c
> index 283be4a..585f599 100644
> --- a/drivers/net/wireless/prism54/isl_ioctl.c
> +++ b/drivers/net/wireless/prism54/isl_ioctl.c
> @@ -1853,7 +1853,6 @@ prism54_del_mac(struct net_device *ndev, struct iw_request_info *info,
> islpci_private *priv = netdev_priv(ndev);
> struct islpci_acl *acl = &priv->acl;
> struct mac_entry *entry;
> - struct list_head *ptr;
> struct sockaddr *addr = (struct sockaddr *) extra;
>
> if (addr->sa_family != ARPHRD_ETHER)
> @@ -1861,11 +1860,9 @@ prism54_del_mac(struct net_device *ndev, struct iw_request_info *info,
>
> if (down_interruptible(&acl->sem))
> return -ERESTARTSYS;
> - for (ptr = acl->mac_list.next; ptr != &acl->mac_list; ptr = ptr->next) {
> - entry = list_entry(ptr, struct mac_entry, _list);
> -
> + list_for_each_entry(entry, &acl->mac_list, _list) {
> if (memcmp(entry->addr, addr->sa_data, ETH_ALEN) == 0) {
> - list_del(ptr);
> + list_del(&entry->_list);
> acl->size--;
> kfree(entry);
> up(&acl->sem);
> @@ -1883,7 +1880,6 @@ prism54_get_mac(struct net_device *ndev, struct iw_request_info *info,
> islpci_private *priv = netdev_priv(ndev);
> struct islpci_acl *acl = &priv->acl;
> struct mac_entry *entry;
> - struct list_head *ptr;
> struct sockaddr *dst = (struct sockaddr *) extra;
>
> dwrq->length = 0;
> @@ -1891,9 +1887,7 @@ prism54_get_mac(struct net_device *ndev, struct iw_request_info *info,
> if (down_interruptible(&acl->sem))
> return -ERESTARTSYS;
>
> - for (ptr = acl->mac_list.next; ptr != &acl->mac_list; ptr = ptr->next) {
> - entry = list_entry(ptr, struct mac_entry, _list);
> -
> + list_for_each_entry(entry, &acl->mac_list, _list) {
> memcpy(dst->sa_data, entry->addr, ETH_ALEN);
> dst->sa_family = ARPHRD_ETHER;
> dwrq->length++;
> @@ -1960,7 +1954,6 @@ prism54_get_policy(struct net_device *ndev, struct iw_request_info *info,
> static int
> prism54_mac_accept(struct islpci_acl *acl, char *mac)
> {
> - struct list_head *ptr;
> struct mac_entry *entry;
> int res = 0;
>
> @@ -1972,8 +1965,7 @@ prism54_mac_accept(struct islpci_acl *acl, char *mac)
> return 1;
> }
>
> - for (ptr = acl->mac_list.next; ptr != &acl->mac_list; ptr = ptr->next) {
> - entry = list_entry(ptr, struct mac_entry, _list);
> + list_for_each_entry(entry, &acl->mac_list, _list) {
> if (memcmp(entry->addr, mac, ETH_ALEN) == 0) {
> res = 1;
> break;
> @@ -2216,11 +2208,9 @@ prism54_wpa_bss_ie_init(islpci_private *priv)
> void
> prism54_wpa_bss_ie_clean(islpci_private *priv)
> {
> - struct list_head *ptr, *n;
> + struct islpci_bss_wpa_ie *bss, *n;
>
> - list_for_each_safe(ptr, n, &priv->bss_wpa_list) {
> - struct islpci_bss_wpa_ie *bss;
> - bss = list_entry(ptr, struct islpci_bss_wpa_ie, list);
> + list_for_each_entry_safe(bss, n, &priv->bss_wpa_list, list) {
> kfree(bss);
> }
> }
>
> --
> Matthias Kaehlcke
> Linux Application Developer
> Barcelona
>
> I am incapable of conceiving infinity, and yet I do not accept finity
> (Simone de Beauvoir)
> .''`.
> using free software / Debian GNU/Linux | http://debian.org : :' :
> `. `'`
> gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4 `-
> -
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2007-05-29 15:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 12:56 [PATCH 0/2] use list_for_each() for iteration in hostap and prism54 driver Matthias Kaehlcke
2007-05-25 13:03 ` [PATCH 1/2] use list_for_each() for iteration in Host AP driver Matthias Kaehlcke
2007-05-25 14:30 ` Christoph Hellwig
2007-05-27 10:28 ` [PATCH 1/2] use list_for_each_entry() for iteration in hostap_ap.c Matthias Kaehlcke
2007-05-28 2:44 ` Jouni Malinen
2007-05-28 6:45 ` Matthias Kaehlcke
2007-05-25 13:04 ` [PATCH 2/2] use list_for_each() for iteration in Prism 54 driver Matthias Kaehlcke
2007-05-27 10:39 ` [PATCH 2/2] use list_for_each_entry() " Matthias Kaehlcke
2007-05-29 15:38 ` Luis R. Rodriguez [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=43e72e890705290838o50fd0897re3f8fc7547b3758e@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=developers@islsm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=matthias.kaehlcke@gmail.com \
/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
all inboxes | Powered by JetHome®