From: Brian Norris <computersforpeace@gmail.com>
To: Jingoo Han <jg1.han@samsung.com>
Cc: "'David Woodhouse'" <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/8] mtd: Remove unnecessary OOM messages
Date: Tue, 11 Feb 2014 10:50:13 -0800 [thread overview]
Message-ID: <20140211185013.GH18440@ld-irv-0074> (raw)
In-Reply-To: <000201cf2301$b168d250$143a76f0$%han@samsung.com>
On Thu, Feb 06, 2014 at 03:07:19PM +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().
>
> Jingoo Han (8):
> mtd: devices: elm: Remove unnecessary OOM messages
> mtd: spear_smi: Remove unnecessary OOM messages
> mtd: pmc551: Remove unnecessary OOM messages
> mtd: plat-ram: Remove unnecessary OOM messages
> mtd: lpddr: Remove unnecessary OOM messages
> mtd: onenand: Remove unnecessary OOM messages
> mtd: cfi: Remove unnecessary OOM messages
> mtd: gen_probe: Remove unnecessary OOM messages
Pushed all 8 to l2-mtd.git. Thanks.
Have you ever considered using a tool like coccinelle to do this sort of
work? You send so many of these boilerplate patch series, I would think
it would help everyone to just get them out of the way with scripted
assistance. And you could then more easily catch new introductions if
they slip through the review process.
Brian
parent reply other threads:[~2014-02-11 18:50 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <000201cf2301$b168d250$143a76f0$%han@samsung.com>]
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=20140211185013.GH18440@ld-irv-0074 \
--to=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=jg1.han@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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
all inboxes | Powered by JetHome®