From: Felipe Balbi <balbi@ti.com>
To: Luciano Coelho <coelho@ti.com>
Cc: linville@tuxdriver.com, sfr@canb.auug.org.au, joe@perches.com,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH v2] wlcore: remove newly introduced alloc/OOM messages
Date: Mon, 11 Feb 2013 10:24:55 +0200 [thread overview]
Message-ID: <20130211082455.GC25438@arwen.pp.htv.fi> (raw)
In-Reply-To: <1360570878-23107-1-git-send-email-coelho@ti.com>
[-- Attachment #1: Type: text/plain, Size: 482 bytes --]
On Mon, Feb 11, 2013 at 10:21:18AM +0200, Luciano Coelho wrote:
> In commit 0d2e7a5c (wireless: Remove unnecessary alloc/OOM messages,
> alloc cleanups) OOM messages after alloc were removed from the wlcore
> modules.
>
> Commit afb43e6d (wlcore: remove if_ops from platform_data)
> reintroduced a couple of those. This patch removes them.
>
> Signed-off-by: Luciano Coelho <coelho@ti.com>
looks good now :-)
Reviewed-by: Felipe Balbi <balbi@ti.com>
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-02-11 8:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 2:33 linux-next: manual merge of the wireless-next tree with the net-next tree Stephen Rothwell
2013-02-11 2:58 ` Joe Perches
2013-02-11 6:47 ` Luciano Coelho
2013-02-11 7:40 ` Stephen Rothwell
2013-02-11 7:53 ` Luciano Coelho
2013-02-11 8:02 ` [PATCH] wlcore: remove newly introduced alloc/OOM messages Luciano Coelho
2013-02-11 8:06 ` Luciano Coelho
2013-02-11 8:07 ` Joe Perches
2013-02-11 8:07 ` Luciano Coelho
2013-02-11 8:08 ` Felipe Balbi
2013-02-11 8:21 ` [PATCH v2] " Luciano Coelho
2013-02-11 8:24 ` Felipe Balbi [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=20130211082455.GC25438@arwen.pp.htv.fi \
--to=balbi@ti.com \
--cc=coelho@ti.com \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).