From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Jingoo Han <jg1.han@samsung.com>
Cc: "'Chanwoo Choi'" <cw00.choi@samsung.com>,
"'MyungJoo Ham'" <myungjoo.ham@samsung.com>,
linux-kernel@vger.kernel.org,
"'Krzysztof Kozlowski'" <k.kozlowski@samsung.com>
Subject: Re: [PATCH] extcon: Remove unnecessary OOM messages
Date: Wed, 18 Jun 2014 10:06:16 +0100 [thread overview]
Message-ID: <20140618090615.GA3412@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <000401cf8ab6$6613d350$323b79f0$%han@samsung.com>
On Wed, Jun 18, 2014 at 02:30:21PM +0900, Jingoo Han wrote:
> The site-specific OOM messages are unnecessary, because they
> duplicate the MM subsystem generic OOM message. The following
> checkpatch warning is also removed.
>
> WARNING: Possible unnecessary 'out of memory' message
>
> Signed-off-by: Jingoo Han <jg1.han@samsung.com>
> ---
For the Arizona bit:
Acked-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Thanks,
Charles
next prev parent reply other threads:[~2014-06-18 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 5:30 [PATCH] extcon: Remove unnecessary OOM messages Jingoo Han
2014-06-18 9:06 ` Charles Keepax [this message]
2014-06-20 1:13 ` Chanwoo Choi
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=20140618090615.GA3412@opensource.wolfsonmicro.com \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=cw00.choi@samsung.com \
--cc=jg1.han@samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.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).