From: "John W. Linville" <linville@tuxdriver.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Arend van Spriel <arend@broadcom.com>,
Chen-Yu Tsai <wens@csie.org>,
linux-wireless@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
devicetree <devicetree@vger.kernel.org>,
linux-sunxi@googlegroups.com
Subject: Re: [PATCH v4 0/4] brcmfmac: OOB interrupt support
Date: Tue, 15 Jul 2014 16:58:41 -0400 [thread overview]
Message-ID: <20140715205841.GG26012@tuxdriver.com> (raw)
In-Reply-To: <1404051421-24377-1-git-send-email-hdegoede@redhat.com>
The patch "brcmfmac: Cleanup used device IDs." makes this series
not build. Unfortunately, I already merged that one...
Would you mind rebasing/reposting this?
Sorry...
John
On Sun, Jun 29, 2014 at 04:16:57PM +0200, Hans de Goede wrote:
> Hi All,
>
> Here is v2 of the brcmfmac: OOB interrupt support series.
>
> Changes since v1:
> -Post as a stand alone series, rather then together with sunxi pinctrl changes,
> etc.
> -Add a patch to fixup the names of the register addresses used in the
> "brcmfmac: Fix OOB interrupt not working for BCM43362" patch
> -Use the new register names in:
> "brcmfmac: Fix OOB interrupt not working for BCM43362"
>
> Changes since v2:
> -"dt: bindings: add bindings for Broadcom bcm43xx sdio devices"
> * changed the compatible string to brcm,bcm4329-fmac
> * replaced the dt-bindings example with a real world example
> -"brcmfmac: Fix OOB interrupt not working for BCM43362"
> * updated commit message with confirmation from broadcom that this is the
> right thing to do
>
> Regards,
>
> Hans
>
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2014-07-15 21:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-29 14:16 [PATCH v4 0/4] brcmfmac: OOB interrupt support Hans de Goede
2014-06-29 14:16 ` [PATCH v3 1/4] dt: bindings: add bindings for Broadcom bcm43xx sdio devices Hans de Goede
2014-06-30 8:31 ` Arend van Spriel
2014-06-30 9:09 ` Hans de Goede
2014-07-07 18:23 ` John W. Linville
2014-07-08 6:55 ` [linux-sunxi] " Hans de Goede
2014-06-29 14:16 ` [PATCH v3 2/4] brcmfmac: add device tree support for SDIO devices Hans de Goede
2014-06-29 14:17 ` [PATCH v3 3/4] brcmfmac: Fix some wrong register defines Hans de Goede
2014-06-29 14:17 ` [PATCH v3 4/4] brcmfmac: Fix OOB interrupt not working for BCM43362 Hans de Goede
2014-06-30 8:15 ` [PATCH v4 0/4] brcmfmac: OOB interrupt support Arend van Spriel
2014-07-15 20:58 ` John W. Linville [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=20140715205841.GG26012@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=arend@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=hdegoede@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sunxi@googlegroups.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wens@csie.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).