From: Fabian Frederick <fabf@skynet.be>
To: linux-kernel@vger.kernel.org
Cc: davem@davemloft.net, Fabian Frederick <fabf@skynet.be>,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
brcm80211-dev-list@broadcom.com
Subject: [PATCH 0/4 linux-next] drivers/net: use container_of where possible
Date: Sat, 13 Sep 2014 22:38:25 +0200 [thread overview]
Message-ID: <1410640709-18295-1-git-send-email-fabf@skynet.be> (raw)
Small patchset using container_of instead of casting on first structure member address.
Fabian Frederick (4):
net: fec: use container_of to resolve bufdesc_ex from bufdesc
bna: use container_of to resolve bufdesc_ex from bufdesc
brcm80211: use container_of to resolve brcms_phy from brcms_phy_pub
brcm80211: use container_of to resolve dma_info from dma_pub
drivers/net/ethernet/brocade/bna/bna_enet.c | 9 +-
drivers/net/ethernet/brocade/bna/bna_tx_rx.c | 4 +-
drivers/net/ethernet/freescale/fec_main.c | 4 +-
drivers/net/wireless/brcm80211/brcmsmac/dma.c | 38 +++----
.../net/wireless/brcm80211/brcmsmac/phy/phy_cmn.c | 122 ++++++++++-----------
.../net/wireless/brcm80211/brcmsmac/phy/phy_lcn.c | 6 +-
.../net/wireless/brcm80211/brcmsmac/phy/phy_n.c | 8 +-
7 files changed, 97 insertions(+), 94 deletions(-)
--
1.8.4.5
next reply other threads:[~2014-09-13 20:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-13 20:38 Fabian Frederick [this message]
2014-09-13 20:38 ` [PATCH 1/4 linux-next] net: fec: use container_of to resolve bufdesc_ex from bufdesc Fabian Frederick
2014-09-15 16:49 ` David Miller
2014-09-13 20:38 ` [PATCH 2/4 linux-next] bna: " Fabian Frederick
2014-09-15 16:49 ` David Miller
2014-09-13 20:38 ` [PATCH 3/4 linux-next] brcm80211: use container_of to resolve brcms_phy from brcms_phy_pub Fabian Frederick
2014-09-13 20:38 ` [PATCH 4/4 linux-next] brcm80211: use container_of to resolve dma_info from dma_pub Fabian Frederick
2014-09-14 7:32 ` [PATCH 0/4 linux-next] drivers/net: use container_of where possible Arend van Spriel
2014-09-14 7:32 ` Arend van Spriel
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=1410640709-18295-1-git-send-email-fabf@skynet.be \
--to=fabf@skynet.be \
--cc=brcm80211-dev-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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.