From: Dan Carpenter <error27@gmail.com>
To: Javier Martinez Canillas <martinez.javier@gmail.com>
Cc: Greg KH <greg@kroah.com>,
devel@driverdev.osuosl.org, Dowan Kim <dowan@broadcom.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
linux-wireless@vger.kernel.org, arend@broadcom.com
Subject: Re: [PATCH 2/2] staging: brcm80211: Remove unused variables and code clean up
Date: Tue, 1 Mar 2011 19:03:16 +0300 [thread overview]
Message-ID: <20110301160316.GT18043@bicker> (raw)
In-Reply-To: <AANLkTi=zU-F=y2qn6B90F3esbNVkE6_nCOZS-dnTA4en@mail.gmail.com>
On Tue, Mar 01, 2011 at 04:37:55PM +0100, Javier Martinez Canillas wrote:
> >> ---
> >> drivers/staging/brcm80211/brcmsmac/wlc_mac80211.c | 9 ---------
> >
> > This doesn't apply anymore, care to redo it and resend?
> >
> > thanks,
>
> Sure Greg but I tried with today linux-next and the patch applies
> cleanly. Maybe the problem are some patches that you have but haven't
> reached linux-next yet.
>
> Do you want me to wait a few days to redo and resend it or am I doing
> something wrong?
Actually Arend has a different patch for this, that I guess fixes the
#if 0 code instead of removing it. Probably that's prefered. I've
asked him to submit it.
regards,
dan carpenter
next prev parent reply other threads:[~2011-03-01 16:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-27 20:54 [PATCH 1/2] staging: brcm80211: Add buf_size parameter to ampdu_action handler function Javier Martinez Canillas
2011-02-27 20:54 ` [PATCH 2/2] staging: brcm80211: Remove unused variables and code clean up Javier Martinez Canillas
2011-03-01 3:11 ` Greg KH
2011-03-01 15:37 ` Javier Martinez Canillas
2011-03-01 15:48 ` Greg KH
2011-03-01 16:03 ` Dan Carpenter [this message]
2011-03-03 11:30 ` Javier Martinez Canillas
2011-02-28 9:50 ` [PATCH 1/2] staging: brcm80211: Add buf_size parameter to ampdu_action handler function Roland Vossen
2011-03-02 19:23 ` Arend van Spriel
2011-03-03 11:50 ` Javier Martinez Canillas
2011-03-03 15:38 ` 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=20110301160316.GT18043@bicker \
--to=error27@gmail.com \
--cc=arend@broadcom.com \
--cc=devel@driverdev.osuosl.org \
--cc=dowan@broadcom.com \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=linux-wireless@vger.kernel.org \
--cc=martinez.javier@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).