From: Thierry Reding <thierry.reding@gmail.com>
To: Jingoo Han <jg1.han@samsung.com>
Cc: linux-pwm@vger.kernel.org
Subject: Re: [PATCH RESEND 0/9] pwm: Remove unnecessary OOM messages
Date: Mon, 28 Apr 2014 13:42:58 +0200 [thread overview]
Message-ID: <20140428114257.GJ19455@ulmo> (raw)
In-Reply-To: <000a01cf5ed7$bd178ad0$3746a070$%han@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 1488 bytes --]
On Wed, Apr 23, 2014 at 06:38:09PM +0900, Jingoo Han wrote:
> The site-specific OOM messages are unnecessary, because they
> duplicate the MM subsystem generic OOM message. For example,
> k.alloc and v.alloc failures use dump_stack().
>
> These patches were expected to be applied to 3.15-rc1. [1]
> However, it is not merged yet, so I resend these patches
> based on 3.15-rc2.
>
> [1] http://www.spinics.net/lists/linux-pwm/msg00976.html
>
> Jingoo Han (9):
> pwm: ab8500: Remove unnecessary OOM messages
> pwm: i.MX: Remove unnecessary OOM messages
> pwm: pxa: Remove unnecessary OOM messages
> pwm: renesas-tpu: Remove unnecessary OOM messages
> pwm: spear: Remove unnecessary OOM messages
> pwm: tegra: Remove unnecessary OOM messages
> pwm: pwm-tiecap: Remove unnecessary OOM messages
> pwm: tiehrpwm: Remove unnecessary OOM messages
> pwm: vt8500: Remove unnecessary OOM messages
>
> ---
> drivers/pwm/pwm-ab8500.c | 4 +---
> drivers/pwm/pwm-imx.c | 4 +---
> drivers/pwm/pwm-pxa.c | 4 +---
> drivers/pwm/pwm-renesas-tpu.c | 4 +---
> drivers/pwm/pwm-spear.c | 4 +---
> drivers/pwm/pwm-tegra.c | 4 +---
> drivers/pwm/pwm-tiecap.c | 4 +---
> drivers/pwm/pwm-tiehrpwm.c | 4 +---
> drivers/pwm/pwm-vt8500.c | 4 +---
> 9 files changed, 9 insertions(+), 27 deletions(-)
All 9 patches applied, thanks.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2014-04-28 11:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 9:38 [PATCH RESEND 0/9] pwm: Remove unnecessary OOM messages Jingoo Han
2014-04-23 9:39 ` [PATCH RESEND 1/9] pwm: ab8500: " Jingoo Han
2014-04-23 9:39 ` [PATCH RESEND 2/9] pwm: i.MX: " Jingoo Han
2014-04-23 9:40 ` [PATCH RESEND 3/9] pwm: pxa: " Jingoo Han
2014-04-23 9:40 ` [PATCH RESEND 4/9] pwm: renesas-tpu: " Jingoo Han
2014-04-23 9:40 ` [PATCH RESEND 5/9] pwm: spear: " Jingoo Han
2014-04-23 9:41 ` [PATCH RESEND 6/9] pwm: tegra: " Jingoo Han
2014-04-23 9:41 ` [PATCH RESEND 7/9] pwm: pwm-tiecap: " Jingoo Han
2014-04-23 9:41 ` [PATCH RESEND 8/9] pwm: tiehrpwm: " Jingoo Han
2014-04-23 9:42 ` [PATCH RESEND 9/9] pwm: vt8500: " Jingoo Han
2014-04-28 11:42 ` Thierry Reding [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=20140428114257.GJ19455@ulmo \
--to=thierry.reding@gmail.com \
--cc=jg1.han@samsung.com \
--cc=linux-pwm@vger.kernel.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 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.