From: Jingoo Han <jg1.han@samsung.com>
To: 'Thierry Reding' <thierry.reding@gmail.com>
Cc: linux-pwm@vger.kernel.org, 'Jingoo Han' <jg1.han@samsung.com>
Subject: [PATCH 0/9] pwm: Remove unnecessary OOM messages
Date: Wed, 26 Feb 2014 09:59:29 +0900 [thread overview]
Message-ID: <000701cf328e$00ed24c0$02c76e40$%han@samsung.com> (raw)
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().
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(-)
next reply other threads:[~2014-02-26 0:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 0:59 Jingoo Han [this message]
2014-02-26 1:02 ` [PATCH 1/9] pwm: ab8500: Remove unnecessary OOM messages Jingoo Han
2014-02-26 1:04 ` [PATCH 2/9] pwm: i.MX: " Jingoo Han
2014-02-26 1:06 ` [PATCH 3/9] pwm: pxa: " Jingoo Han
2014-02-26 1:08 ` [PATCH 4/9] pwm: renesas-tpu: " Jingoo Han
2014-02-26 2:22 ` Laurent Pinchart
2014-02-26 2:34 ` Jingoo Han
2014-02-26 22:02 ` Laurent Pinchart
2014-02-26 1:09 ` [PATCH 5/9] pwm: spear: " Jingoo Han
2014-02-26 4:49 ` Viresh Kumar
2014-02-26 4:57 ` Jingoo Han
2014-02-26 5:10 ` Viresh Kumar
2014-02-26 5:19 ` Joe Perches
2014-02-26 6:26 ` Viresh Kumar
2014-03-03 1:14 ` Jingoo Han
2014-03-03 9:53 ` Dan Carpenter
2014-03-05 11:00 ` Laurent Pinchart
2014-03-05 11:40 ` Dan Carpenter
2014-03-05 16:17 ` Viresh Kumar
2014-03-05 16:29 ` Laurent Pinchart
2014-03-07 8:04 ` Jingoo Han
2014-03-10 12:22 ` Thierry Reding
2014-04-03 3:24 ` Jingoo Han
2014-05-21 10:34 ` Thierry Reding
2014-02-26 1:10 ` [PATCH 6/9] pwm: tegra: " Jingoo Han
2014-02-26 1:12 ` [PATCH 7/9] pwm: pwm-tiecap: " Jingoo Han
2014-02-26 1:13 ` [PATCH 8/9] pwm: tiehrpwm: " Jingoo Han
2014-02-26 1:14 ` [PATCH 9/9] pwm: vt8500: " Jingoo Han
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='000701cf328e$00ed24c0$02c76e40$%han@samsung.com' \
--to=jg1.han@samsung.com \
--cc=linux-pwm@vger.kernel.org \
--cc=thierry.reding@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 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).