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>
Subject: Re: [09/11] brcmfmac: Remove array of functions
Date: Tue, 09 Jan 2018 14:27:48 +0200 [thread overview]
Message-ID: <87mv1n1akb.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <5A54B4BC.4070800@broadcom.com> (Arend van Spriel's message of "Tue, 9 Jan 2018 13:25:32 +0100")
Arend van Spriel <arend.vanspriel@broadcom.com> writes:
> On 1/8/2018 6:20 PM, Kalle Valo wrote:
>> Arend Van Spriel <arend.vanspriel@broadcom.com> wrote:
>>
>>> Replace the array of functions with a pair of pointers to the
>>> relevant functions.
>>>
>>> Signed-off-by: Ian Molton <ian@mnementh.co.uk>
>>> Acked-by: Arend van Spriel <arend.vanspriel@broadcom.com>
>>> Signed-off-by: Arend van Spriel <arend.vanspriel@broadcom.com>
>>
>> Failed to apply:
>>
>> fatal: sha1 information is lacking or useless
>> (drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c).
>> error: could not build fake ancestor
>> Applying: brcmfmac: Remove array of functions
>> Patch failed at 0001 brcmfmac: Remove array of functions
>> The copy of the patch that failed is found in: .git/rebase-apply/patch
>
> Guess you merged wireless-drivers/master in between.
Actually fast forwarded to latest net-next, so I got the latest
wireless-drivers via that route.
> I just rebased and resolved the conflict and sent a V2 with the
> remaining patches.
Saw them, thanks.
--
Kalle Valo
next prev parent reply other threads:[~2018-01-09 12:27 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 ` [01/11] " Kalle Valo
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 [this message]
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=87mv1n1akb.fsf@kamboji.qca.qualcomm.com \
--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).