linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Arend van Spriel <arend@broadcom.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 04/10] brcmfmac: get rid of duplicate SDIO device identifiers
Date: Tue, 06 Jan 2015 20:35:39 +0200	[thread overview]
Message-ID: <87k30zycxw.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1419162233-19492-5-git-send-email-arend@broadcom.com> (Arend van Spriel's message of "Sun, 21 Dec 2014 12:43:47 +0100")

Arend van Spriel <arend@broadcom.com> writes:

> Instead of defining SDIO device identifier in brcm80211 code use
> the defintions in linux/mmc/sdio_ids.h directly.
>
> Reviewed-by: Hante Meuleman <meuleman@broadcom.com>
> Reviewed-by: Pieter-Paul Giesberts <pieterpg@broadcom.com>
> Signed-off-by: Arend van Spriel <arend@broadcom.com>

I tried to apply this but got:

Applying: brcmfmac: get rid of duplicate SDIO device identifiers
error: patch failed: drivers/net/wireless/brcm80211/brcmfmac/bcmsdh.c:996
error: drivers/net/wireless/brcm80211/brcmfmac/bcmsdh.c: patch does not apply
error: patch failed: drivers/net/wireless/brcm80211/include/brcm_hw_ids.h:46
error: drivers/net/wireless/brcm80211/include/brcm_hw_ids.h: patch does not apply
Patch failed at 0001 brcmfmac: get rid of duplicate SDIO device identifiers

Please resend.

-- 
Kalle Valo

  reply	other threads:[~2015-01-06 18:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-21 11:43 [PATCH 00/10] brcmfmac: new device support and more Arend van Spriel
2014-12-21 11:43 ` [PATCH 01/10] brcmfmac: Fix incorrect casting of 64 bit physical address Arend van Spriel
2014-12-21 17:24   ` Joe Perches
2014-12-21 11:43 ` [PATCH 02/10] brcmfmac: Fix possible dereference of NULL pointer Arend van Spriel
2014-12-23 17:07   ` Arend van Spriel
2014-12-21 11:43 ` [PATCH 03/10] brcmfmac: Add support for bcm43340/1 wireless chipsets Arend van Spriel
2014-12-21 17:50   ` Marcel Holtmann
2014-12-21 19:56     ` Arend van Spriel
2014-12-21 20:14       ` Rafał Miłecki
2014-12-22  9:05         ` Arend van Spriel
2014-12-22  9:33           ` Rafał Miłecki
2014-12-21 11:43 ` [PATCH 04/10] brcmfmac: get rid of duplicate SDIO device identifiers Arend van Spriel
2015-01-06 18:35   ` Kalle Valo [this message]
2014-12-21 11:43 ` [PATCH 05/10] brcmfmac: remove unused/duplicate defines in chip.c Arend van Spriel
2014-12-21 11:43 ` [PATCH 06/10] brcmfmac: Fix WEP configuration for AP mode Arend van Spriel
2014-12-21 11:43 ` [PATCH 07/10] brcmfmac: Change error log in standard log for rxbufpost Arend van Spriel
2014-12-21 11:43 ` [PATCH 08/10] brcmfmac: follow user-space regulatory domain selection Arend van Spriel
2014-12-21 11:43 ` [PATCH 09/10] brcmfmac: signal completion of 802.1x Arend van Spriel
2014-12-21 11:43 ` [PATCH 10/10] brcmfmac: enable 802.11d support in firmware Arend van Spriel
2015-01-06 18:36 ` [PATCH 00/10] brcmfmac: new device support and more Kalle Valo
2015-01-06 19:07   ` 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=87k30zycxw.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=arend@broadcom.com \
    --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).