All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Stultz <johnstul@us.ibm.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	open list <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org
Subject: Re: [patch] clocksource: clean up parse_pmtmr()
Date: Tue, 13 Nov 2012 19:05:33 +0000	[thread overview]
Message-ID: <50A299FD.2060409@us.ibm.com> (raw)
In-Reply-To: <20121020034948.GV5685@mwanda>

On 10/19/2012 09:46 PM, Dan Carpenter wrote:
> I changed the strict_strtoul() to kstrtouint().  That has the check
> for UINT_MAX built in to it so the ifdefs can be removed.  Also
> I changed a printk() to pr_info().
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Applied. Thanks!
-john


WARNING: multiple messages have this Message-ID (diff)
From: John Stultz <johnstul@us.ibm.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	open list <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org
Subject: Re: [patch] clocksource: clean up parse_pmtmr()
Date: Tue, 13 Nov 2012 11:05:33 -0800	[thread overview]
Message-ID: <50A299FD.2060409@us.ibm.com> (raw)
In-Reply-To: <20121020034948.GV5685@mwanda>

On 10/19/2012 09:46 PM, Dan Carpenter wrote:
> I changed the strict_strtoul() to kstrtouint().  That has the check
> for UINT_MAX built in to it so the ifdefs can be removed.  Also
> I changed a printk() to pr_info().
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Applied. Thanks!
-john


  reply	other threads:[~2012-11-13 19:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-20  4:46 [patch] clocksource: clean up parse_pmtmr() Dan Carpenter
2012-10-20  4:46 ` Dan Carpenter
2012-11-13 19:05 ` John Stultz [this message]
2012-11-13 19:05   ` John Stultz

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=50A299FD.2060409@us.ibm.com \
    --to=johnstul@us.ibm.com \
    --cc=dan.carpenter@oracle.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.