linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 3/8] bcma: add agent IOCTL bit values for Broadcom 802.11 and CR4 cores
Date: Thu, 16 Jan 2014 13:50:16 -0500	[thread overview]
Message-ID: <20140116185015.GC10165@tuxdriver.com> (raw)
In-Reply-To: <52D6AA49.6000707@broadcom.com>

On Wed, Jan 15, 2014 at 04:33:29PM +0100, Arend van Spriel wrote:
> On 01/14/2014 07:29 AM, Rafał Miłecki wrote:
> > 2014/1/13 Arend van Spriel <arend@broadcom.com>:
> >> The IOCTL register in the agent/wrapper contains additional bits
> >> that are core specific and use in the core reset sequence.
> > 
> > I'm not sure about this. I don't think we want to keep device-specific
> > bits in a commond (bcma's) code.
> 
> Hi John,
> 
> Given that I agree with Rafał's argument, can you drop patch #3 from
> this series. I applied the other patches using 'git am -3' and that
> works. Let me know if I should resend them.
> 
> Gr. AvS

OK.

-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2014-01-16 19:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13 21:20 [PATCH 0/8] brcmfmac: cleanup work for 3.14 Arend van Spriel
2014-01-13 21:20 ` [PATCH 1/8] brcmfmac: Create common nvram parsing routines Arend van Spriel
2014-01-13 21:20 ` [PATCH 2/8] brcmfmac: update core reset and disable routines Arend van Spriel
2014-01-13 21:20 ` [PATCH 3/8] bcma: add agent IOCTL bit values for Broadcom 802.11 and CR4 cores Arend van Spriel
2014-01-14  6:29   ` Rafał Miłecki
2014-01-14 16:05     ` Arend van Spriel
2014-01-14 19:25       ` Rafał Miłecki
2014-01-15 15:45         ` Arend van Spriel
2014-01-15 15:33     ` Arend van Spriel
2014-01-16 18:50       ` John W. Linville [this message]
2014-01-13 21:20 ` [PATCH 4/8] brcmfmac: rework firmware download code Arend van Spriel
2014-01-13 21:20 ` [PATCH 5/8] brcmfmac: restructure brcmf_sdio_chip_recognition() Arend van Spriel
2014-01-13 21:20 ` [PATCH 6/8] brcmfmac: rename chip and core related structures Arend van Spriel
2014-01-13 21:20 ` [PATCH 7/8] brcmfmac: initialize escan function pointer during scheduled scan Arend van Spriel
2014-01-13 21:20 ` [PATCH 8/8] brcmfmac: handle SDIO card removal 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=20140116185015.GC10165@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=arend@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=zajec5@gmail.com \
    /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).