From: Peter Zijlstra <peterz@infradead.org>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: mingo@redhat.com, Mark Rustad <mark.d.rustad@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] semaphore: Resolve some shadow warnings
Date: Mon, 1 Sep 2014 14:02:44 +0200 [thread overview]
Message-ID: <20140901120244.GI27892@worktop.ger.corp.intel.com> (raw)
In-Reply-To: <1409228366-7027-1-git-send-email-jeffrey.t.kirsher@intel.com>
On Thu, Aug 28, 2014 at 05:19:26AM -0700, Jeff Kirsher wrote:
> From: Mark Rustad <mark.d.rustad@intel.com>
>
> Resolve some shadow warnings resulting from using the name
> jiffies, which is a well-known global. This is not a problem
> of course, but it could be a trap for someone copying and
> pasting code, and it just makes W=2 a little cleaner.
>
> Signed-off-by: Mark Rustad <mark.d.rustad@intel.com>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Why isn't Mark sending this email?
> ---
> kernel/locking/semaphore.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/kernel/locking/semaphore.c b/kernel/locking/semaphore.c
> index 6815171..7782dbc 100644
> --- a/kernel/locking/semaphore.c
> +++ b/kernel/locking/semaphore.c
> @@ -36,7 +36,7 @@
> static noinline void __down(struct semaphore *sem);
> static noinline int __down_interruptible(struct semaphore *sem);
> static noinline int __down_killable(struct semaphore *sem);
> -static noinline int __down_timeout(struct semaphore *sem, long jiffies);
> +static noinline int __down_timeout(struct semaphore *sem, long njiffies);
> static noinline void __up(struct semaphore *sem);
So what's wrong with calling it "timeout" instead? That's what most
other sites do.
next prev parent reply other threads:[~2014-09-01 12:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 12:19 [PATCH] semaphore: Resolve some shadow warnings Jeff Kirsher
2014-09-01 12:02 ` Peter Zijlstra [this message]
2014-09-01 23:41 ` Jeff Kirsher
2014-09-02 21:16 ` Rustad, Mark D
2014-09-03 9:39 ` Peter Zijlstra
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=20140901120244.GI27892@worktop.ger.corp.intel.com \
--to=peterz@infradead.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.d.rustad@intel.com \
--cc=mingo@redhat.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