From: David Miller <davem@davemloft.net>
To: joe@perches.com
Cc: fengguang.wu@intel.com, netdev@vger.kernel.org,
linux-wimax@intel.com, wimax@linuxwimax.org
Subject: Re: [PATCH] drivers: net: misc: Remove unused OOM variables
Date: Wed, 06 Feb 2013 15:02:58 -0500 (EST) [thread overview]
Message-ID: <20130206.150258.701602632249933551.davem@davemloft.net> (raw)
In-Reply-To: <1360038149.4849.11.camel@joe-AO722>
From: Joe Perches <joe@perches.com>
Date: Mon, 04 Feb 2013 20:22:29 -0800
> commits 9d11bd159
> ("wimax: Remove unnecessary alloc/OOM messages, alloc cleanups")
> and b2adaca92
> ("ethernet: Remove unnecessary alloc/OOM messages, alloc cleanups")
> added a couple of unused variable warnings.
>
> Remove the now unused variables.
>
> Noticed-by: kbuild test robot <fengguang.wu@intel.com>
> Signed-off-by: Joe Perches <joe@perches.com>
Applied.
prev parent reply other threads:[~2013-02-06 20:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51108250.mCy4M9/YF2ueqPWm%fengguang.wu@intel.com>
2013-02-05 4:22 ` [PATCH] drivers: net: misc: Remove unused OOM variables Joe Perches
2013-02-06 20:02 ` David Miller [this message]
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=20130206.150258.701602632249933551.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=fengguang.wu@intel.com \
--cc=joe@perches.com \
--cc=linux-wimax@intel.com \
--cc=netdev@vger.kernel.org \
--cc=wimax@linuxwimax.org \
/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