linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: linux-wireless@vger.kernel.org, Ian Molton <ian@mnementh.co.uk>,
	Arend van Spriel <arend.vanspriel@broadcom.com>
Subject: Re: [01/11] brcmfmac: Remove {r,w}_sdreg32
Date: Mon,  8 Jan 2018 17:19:11 +0000 (UTC)	[thread overview]
Message-ID: <20180108171911.EBE0B6079C@smtp.codeaurora.org> (raw)
In-Reply-To: <1513687637-5555-2-git-send-email-arend.vanspriel@broadcom.com>

Arend Van Spriel <arend.vanspriel@broadcom.com> wrote:

> From: Ian Molton <ian@mnementh.co.uk>
> 
> Remove yet another IO function from the code and replace with one
> that already exists.
> 
> Signed-off-by: Ian Molton <ian@mnementh.co.uk>
> Reviewed-by: Arend van Spriel <arend.vanspriel@broadcom.com>
> [arend: keep address calculation, ie. (base + offset) in one line]
> Signed-off-by: Arend van Spriel <arend.vanspriel@broadcom.com>

8 patches applied to wireless-drivers-next.git, thanks.

3d110df8f747 brcmfmac: Remove {r,w}_sdreg32
dbda7dacb79a brcmfmac: Rename buscore to core for consistency
874bb8e49b7c brcmfmac: stabilise the value of ->sbwad in use for some xfer routines.
508422f3695b brcmfmac: Correctly handle accesses to SDIO func0
99d7b6fdfc8c brcmfmac: Remove func0 from function array
bcadaaa097c7 brcmfmac: More efficient and slightly easier to read fixup for 4339 chips
00eb62cfc5f8 brcmfmac: Replace function index with function pointer
9c3438ed215a brcmfmac: Clean up interrupt macros

-- 
https://patchwork.kernel.org/patch/10123219/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2018-01-08 17:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-19 12:47 [PATCH 00/11] brcmfmac: restructuring sdio access functions - final drop Arend van Spriel
2017-12-19 12:47 ` [PATCH 01/11] brcmfmac: Remove {r,w}_sdreg32 Arend van Spriel
2018-01-08 17:19   ` Kalle Valo [this message]
2017-12-19 12:47 ` [PATCH 02/11] brcmfmac: Rename buscore to core for consistency Arend van Spriel
2017-12-19 12:47 ` [PATCH 03/11] brcmfmac: stabilise the value of ->sbwad in use for some xfer routines Arend van Spriel
2017-12-19 12:47 ` [PATCH 04/11] brcmfmac: Correctly handle accesses to SDIO func0 Arend van Spriel
2017-12-19 12:47 ` [PATCH 05/11] brcmfmac: Remove func0 from function array Arend van Spriel
2017-12-19 12:47 ` [PATCH 06/11] brcmfmac: More efficient and slightly easier to read fixup for 4339 chips Arend van Spriel
2017-12-19 12:47 ` [PATCH 07/11] brcmfmac: Replace function index with function pointer Arend van Spriel
2017-12-19 12:47 ` [PATCH 08/11] brcmfmac: Clean up interrupt macros Arend van Spriel
2017-12-19 12:47 ` [PATCH 09/11] brcmfmac: Remove array of functions Arend van Spriel
2018-01-08 17:20   ` [09/11] " Kalle Valo
     [not found]   ` <20180108172042.EE67E60818@smtp.codeaurora.org>
2018-01-09 12:25     ` Arend van Spriel
2018-01-09 12:27       ` Kalle Valo
2017-12-19 12:47 ` [PATCH 10/11] brcmfmac: add comment block in brcmf_sdio_buscore_read() Arend van Spriel
2017-12-19 12:47 ` [PATCH 11/11] brcmfmac: rename brcmf_sdiod_buff_{read,write}() functions 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=20180108171911.EBE0B6079C@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=arend.vanspriel@broadcom.com \
    --cc=ian@mnementh.co.uk \
    --cc=linux-wireless@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).