From: Kevin McKinney <klmckinney1@gmail.com>
To: Marcos Paulo de Souza <marcos.souza.org@gmail.com>,
klmckinney1@gmail.com
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, dan.carpenter@oracle.com,
standby24x7@gmail.com
Subject: Re: [PATCH 0/3] staging: bcm: Cleanup bcm driver
Date: Mon, 9 Jul 2012 22:40:47 -0400 [thread overview]
Message-ID: <20120710024046.GA8894@gmail.com> (raw)
In-Reply-To: <1341883960-21635-1-git-send-email-marcos.souza.org@gmail.com>
On Mon, Jul 09, 2012 at 10:32:37PM -0300, Marcos Paulo de Souza wrote:
> Hi Kernel guys!
>
> This new patchset tries to clean a little the bcm driver, removing
> some unused macros and some dead code.
>
> These macros and dead code were reported by the forgotten-macros tool
> (https://github.com/marcosps/forgotten_macros).
>
> The tool is under development, but all the patches looks like OK.
>
> This patchset is based in staging-next.
>
> Thanks guys!
The patchset looks good!
Thanks,
Kevin
next prev parent reply other threads:[~2012-07-10 2:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 1:32 [PATCH 0/3] staging: bcm: Cleanup bcm driver Marcos Paulo de Souza
2012-07-10 1:32 ` [PATCH 1/3] staging: bcm: Remove code that will never execute Marcos Paulo de Souza
2012-07-10 1:32 ` [PATCH 2/3] staging: bcm: Remove all commented macros Marcos Paulo de Souza
2012-07-10 1:32 ` [PATCH 3/3] staging: bcm: Misc.c: Remove unused macros Marcos Paulo de Souza
2012-07-10 2:40 ` Kevin McKinney [this message]
2012-07-10 2:48 ` [PATCH 0/3] staging: bcm: Cleanup bcm driver Marcos Souza
2012-07-10 12:38 ` Kevin McKinney
2012-07-10 12:51 ` Dan Carpenter
2012-07-10 13:24 ` Kevin McKinney
2012-07-10 13:31 ` Dan Carpenter
2012-07-10 13:47 ` Kevin McKinney
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=20120710024046.GA8894@gmail.com \
--to=klmckinney1@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcos.souza.org@gmail.com \
--cc=standby24x7@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.