From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Pranith Kumar <pranith@gatech.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] include/linux/torture.h: remove unused duplicate definition
Date: Wed, 16 Apr 2014 14:45:41 -0700 [thread overview]
Message-ID: <20140416214541.GB4496@linux.vnet.ibm.com> (raw)
In-Reply-To: <534EEC09.7010300@gatech.edu>
On Wed, Apr 16, 2014 at 04:46:01PM -0400, Pranith Kumar wrote:
> remove an unused duplicate definition of torture_param
>
> Signed-off-by: Pranith Kumar <bobby.prani@gmail.com>
This one confused me at first because I could only find one torture_param().
I applied the patch anyway, and it built without errors. I looked more
closely and realized that the names aren't quite the same. The one you
removed has only one "a" in the name, and the one remaining has two "a"s
in its name. ;-)
Good eyes! I updated the title and commit log and queued for 3.16.
Thanx, Paul
> ---
> include/linux/torture.h | 6 ------
> 1 file changed, 6 deletions(-)
>
> diff --git a/include/linux/torture.h b/include/linux/torture.h
> index b2e2b46..88a84a2 100644
> --- a/include/linux/torture.h
> +++ b/include/linux/torture.h
> @@ -49,12 +49,6 @@
> #define VERBOSE_TOROUT_ERRSTRING(s) \
> do { if (verbose) pr_alert("%s" TORTURE_FLAG "!!! %s\n", torture_type, s); } while (0)
>
> -/* Definitions for a non-string torture-test module parameter. */
> -#define torture_parm(type, name, init, msg) \
> - static type name = init; \
> - module_param(name, type, 0444); \
> - MODULE_PARM_DESC(name, msg);
> -
> /* Definitions for online/offline exerciser. */
> int torture_onoff_init(long ooholdoff, long oointerval);
> char *torture_onoff_stats(char *page);
> --
> 1.7.9.5
>
prev parent reply other threads:[~2014-04-16 21:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 20:46 [PATCH 1/2] include/linux/torture.h: remove unused duplicate definition Pranith Kumar
2014-04-16 21:45 ` Paul E. McKenney [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=20140416214541.GB4496@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pranith@gatech.edu \
/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