From: Greg KH <greg@kroah.com>
To: Nohee Ko <noheek@broadcom.com>
Cc: "gregkh@suse.de" <gregkh@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Roman Baker <romanb@broadcom.com>,
David Milne <davidm@broadcom.com>, Venkat Rao <vrao@broadcom.com>,
Howard Harte <hharte@broadcom.com>,
Brett Rudley <brudley@broadcom.com>,
Henry Ptasinski <henryp@broadcom.com>
Subject: Re: [PATCH] staging: brcm80211: add fullmac driver
Date: Mon, 20 Sep 2010 20:54:35 -0700 [thread overview]
Message-ID: <20100921035435.GA31538@kroah.com> (raw)
In-Reply-To: <FD96C117992C584DBC47231B1EB6F5568206497F85@SJEXCHCCR02.corp.ad.broadcom.com>
On Mon, Sep 20, 2010 at 07:43:22PM -0700, Nohee Ko wrote:
> This patch to the existing bcm80211 directory in the staging tree adds fullmac driver support for the BCM4329 SDIO chip from Broadcom. Configuration of the mac80211 driver or the fullmac driver can be done through menuconfig.
Please wrap your lines at 72 columns.
Your patch does not apply to the latest linux-next tree. Your patch is
also mime-encoded which probably doesn't help things.
Care to fix this up and resend it so I can apply it?
> --- a/drivers/staging/brcm80211/util/siutils.c
> +++ b/drivers/staging/brcm80211/util/siutils.c
> @@ -59,12 +59,16 @@ static bool si_buscore_prep(si_info_t *sii, uint bustype, uint devid,
> void *sdh);
> static bool si_buscore_setup(si_info_t *sii, chipcregs_t *cc, uint bustype,
> uint32 savewin, uint *origidx, void *regs);
> +#ifndef BRCM_FULLMAC
> static void si_nvram_process(si_info_t *sii, char *pvars);
> +#endif
>
> /* dev path concatenation util */
> +#ifndef BRCM_FULLMAC
<snip>
Why all the #ifdef mess added to the siutils.c file? Is it really
needed? Why not just leave it alone and have the functions always
build.
thanks,
greg k-h
next prev parent reply other threads:[~2010-09-21 3:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 15:20 [PATCH] staging: brcm80211: Make CFLAGS explicit Tim Gardner
2010-09-17 16:21 ` Greg KH
2010-09-17 17:44 ` Tim Gardner
2010-09-17 17:58 ` Greg KH
2010-09-17 18:03 ` Brett Rudley
2010-09-17 18:33 ` Tim Gardner
2010-09-17 18:39 ` Brett Rudley
[not found] ` <FD96C117992C584DBC47231B1EB6F5568206497F85@SJEXCHCCR02.corp.ad.broadcom.com>
2010-09-21 3:54 ` Greg KH [this message]
2010-09-22 1:56 ` matt mooney
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=20100921035435.GA31538@kroah.com \
--to=greg@kroah.com \
--cc=brudley@broadcom.com \
--cc=davidm@broadcom.com \
--cc=gregkh@suse.de \
--cc=henryp@broadcom.com \
--cc=hharte@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=noheek@broadcom.com \
--cc=romanb@broadcom.com \
--cc=vrao@broadcom.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