From: Julia Lawall <julia.lawall@lip6.fr>
To: Joe Perches <joe@perches.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andy Whitcroft <apw@shadowen.org>,
LKML <linux-kernel@vger.kernel.org>,
Julia Lawall <julia.lawall@lip6.fr>,
benoit.taine@lip6.fr
Subject: Re: [RFC PATCH] checkpatch: Attempt to find unnecessary 'out of memory' messages
Date: Sat, 14 Jun 2014 09:40:52 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1406140937370.2003@localhost6.localdomain6> (raw)
In-Reply-To: <1402502500.6169.5.camel@joe-AO725>
With a semantic patch that searches for the various calls and then a
string containing the letters "emory", I get removals of the messages
below. Do any of these messages look useful? For example, some are
generated with specific functions, such as IRDA_ERROR or BT_ERR. If none
of the messages look useful, should just one big patch go to trivial, or
should the patches go to the individual maintainers?
julia
next prev parent reply other threads:[~2014-06-14 7:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 16:55 Joe Perches
2014-06-11 7:47 ` Dan Carpenter
2014-06-11 16:01 ` Joe Perches
2014-06-14 7:40 ` Julia Lawall [this message]
2014-06-14 8:30 ` Joe Perches
2014-06-14 9:51 ` Julia Lawall
2014-06-18 19:33 ` Paul E. McKenney
2014-06-18 19:49 ` Joe Perches
2014-06-19 21:00 ` Paul E. McKenney
2014-06-19 23:24 ` [RFC PATCH] use snprintf instead of sprintf in rcu_torture_printk Pranith Kumar
2014-06-19 23:33 ` Joe Perches
2014-06-20 0:11 ` Pranith Kumar
2014-06-19 23:49 ` Paul E. McKenney
2014-06-20 0:13 ` Pranith Kumar
2014-06-20 4:54 ` Paul E. McKenney
2014-06-20 22:04 ` Joe Perches
2014-06-18 21:18 ` [RFC PATCH] checkpatch: Attempt to find unnecessary 'out of memory' messages Julia Lawall
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=alpine.DEB.2.02.1406140937370.2003@localhost6.localdomain6 \
--to=julia.lawall@lip6.fr \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=benoit.taine@lip6.fr \
--cc=dan.carpenter@oracle.com \
--cc=joe@perches.com \
--cc=linux-kernel@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 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®