public inbox for b43-dev@lists.infradead.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org,
	Hauke Mehrtens <hauke@hauke-m.de>
Subject: [PATCH] b43: AC-PHY: prepare place for developing new PHY support
Date: Mon, 26 Jan 2015 09:04:33 +0200	[thread overview]
Message-ID: <87egqiggzi.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1422205297-24767-1-git-send-email-zajec5@gmail.com> ("Rafał	Miłecki"'s message of "Sun, 25 Jan 2015 18:01:37 +0100")

Rafa? Mi?ecki <zajec5@gmail.com> writes:

> There are new (not anymore?) Broadcom 802.11ac wireless cards based on
> chipsets like BCM4352 and BCM4360. They use a new PHY type (called
> simply AC) that will require new specific code.
>
> Signed-off-by: Rafa? Mi?ecki <zajec5@gmail.com>
> ---
>
> Kalle: as this commit & Kconfig say, this is just a beginning of new
> PHY type support. In the past we used development model this patch
> follows. Code for new PHY was added patch by patch. Adding everything
> at once would require a huge patchset & development behing the doors.
> Also sending small patches allows better review of changes & should
> result in a better code quality. Let me know if there are any
> problems.

Sounds good to me. Just keep dependency to BROKEN until it's usable and
make sure that the code compiles after every patch.

-- 
Kalle Valo

  reply	other threads:[~2015-01-26  7:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-25 17:01 [PATCH] b43: AC-PHY: prepare place for developing new PHY support Rafał Miłecki
2015-01-26  7:04 ` Kalle Valo [this message]
2015-01-26  8:12   ` Rafał Miłecki

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=87egqiggzi.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=b43-dev@lists.infradead.org \
    --cc=hauke@hauke-m.de \
    --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