From: Rasmus Villemoes <linux@rasmusvillemoes.dk>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
Don Mullis <don.mullis@gmail.com>,
Dave Chinner <david@fromorbit.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] lib: list_sort: Various minor improvements
Date: Thu, 26 Jun 2014 00:28:18 +0200 [thread overview]
Message-ID: <87egycoc8t.fsf@rasmusvillemoes.dk> (raw)
In-Reply-To: <20140625145314.3e16af6998765b7aad860bf7@linux-foundation.org> (Andrew Morton's message of "Wed, 25 Jun 2014 14:53:14 -0700")
Andrew Morton <akpm@linux-foundation.org> writes:
> On Tue, 24 Jun 2014 12:06:27 +0200 Rasmus Villemoes <linux@rasmusvillemoes.dk> wrote:
>
>> Reading the source of lib/list_sort.c, I came up with a few possible
>> improvements. I think 4/4 may be a bit controversial, but 1/4, 2/4 and
>> 3/4 should be straightforward.
>>
>
> All looks OK to me.
Thanks.
> We may as well do the pr_foo() conversion as well. As often happens,
> the results are quite pleasing.
>
> --- a/lib/list_sort.c~lib-list_sortc-convert-to-pr_foo
> +++ a/lib/list_sort.c
> @@ -1,3 +1,6 @@
> +
> +#define pr_fmt(fmt) "list_sort_test: " fmt
> +
> #include <linux/kernel.h>
> #include <linux/module.h>
> #include <linux/list_sort.h>
> @@ -125,9 +128,8 @@ void list_sort(void *priv, struct list_h
> }
> if (lev > max_lev) {
> if (unlikely(lev >= ARRAY_SIZE(part)-1)) {
> - printk_once(KERN_DEBUG "list passed to"
> - " list_sort() too long for"
> - " efficiency\n");
> + pr_debug_once("list passed to list_sort() too "
> + "long for efficiency\n");
Minor comment: Won't this end up saying "list_sort_test: list passed to
...", despite the list coming from a 'real' user? Maybe change the first
#define to '"list_sort: " fmt', the above message to "passed list too
long for efficiency", and redefine pr_fmt right after #ifdef
CONFIG_TEST_LIST_SORT.
Rasmus
next prev parent reply other threads:[~2014-06-25 22:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 10:06 [PATCH v2 0/4] lib: list_sort: Various minor improvements Rasmus Villemoes
2014-06-24 10:06 ` [PATCH v2 1/4] lib: list_sort_test(): Return -ENOMEM when allocation fails Rasmus Villemoes
2014-06-24 10:06 ` [PATCH v2 2/4] lib: list_sort_test(): Add extra corruption check Rasmus Villemoes
2014-06-24 10:06 ` [PATCH v2 3/4] lib: list_sort_test(): Simplify and harden cleanup Rasmus Villemoes
2014-06-24 10:06 ` [PATCH v2 4/4] lib: list_sort.c: Limit number of unused cmp callbacks Rasmus Villemoes
2014-06-25 21:53 ` [PATCH v2 0/4] lib: list_sort: Various minor improvements Andrew Morton
2014-06-25 22:28 ` Rasmus Villemoes [this message]
2014-06-25 22:32 ` Andrew Morton
2014-06-25 22:47 ` Rasmus Villemoes
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=87egycoc8t.fsf@rasmusvillemoes.dk \
--to=linux@rasmusvillemoes.dk \
--cc=akpm@linux-foundation.org \
--cc=artem.bityutskiy@linux.intel.com \
--cc=david@fromorbit.com \
--cc=don.mullis@gmail.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