public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jingoo Han <jg1.han@samsung.com>
To: "'Greg Kroah-Hartman'" <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, "'Arnd Bergmann'" <arnd@arndb.de>,
	"'Michael Hennerich'" <michael.hennerich@analog.com>,
	"'Eric Piel'" <eric.piel@tremplin-utc.net>,
	"'Dimitri Sivanich'" <sivanich@sgi.com>,
	"'Robin Holt'" <holt@sgi.com>,
	"'Andy Shevchenko'" <andy.shevchenko@gmail.com>,
	Jingoo Han <jg1.han@samsung.com>
Subject: Re: [PATCH V3] rtc: rtc-pcf2123: replace strict_strtoul() with kstrtoul()
Date: Fri, 07 Jun 2013 09:57:05 +0900	[thread overview]
Message-ID: <002b01ce6319$ede58fa0$c9b0aee0$@samsung.com> (raw)
In-Reply-To: <20130606195159.GA13011@kroah.com>

On Friday, June 07, 2013 4:52 AM, Greg Kroah-Hartman wrote:
> On Tue, Jun 04, 2013 at 01:12:52PM +0900, Jingoo Han wrote:
> > The usage of strict_strtoul() is not preferred, because
> > strict_strtoul() is obsolete. Thus, kstrtoul() should be
> > used.
> >
> > Signed-off-by: Jingoo Han <jg1.han@samsung.com>
> > Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > ---
> > Changes since v1:
> > - Splitted to two sequential checks.
> > - Added Andy Shevchenko's Reviewed-by.
> >
> > Changes since v1:
> > - Used return code from kstrtoul().
> >
> >  drivers/rtc/rtc-pcf2123.c |   15 ++++++++++-----
> >  1 file changed, 10 insertions(+), 5 deletions(-)
> 
> I'm not the drivers/rtc/ maintainer, why send this to me?

Hi Greg,

Sorry. It's my mistake.
I will re-send it to the maintainer of rtc.
Thank you.

Best regards,
Jingoo Han

> 
> greg k-h


  reply	other threads:[~2013-06-07  0:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-04  4:12 [PATCH V3] rtc: rtc-pcf2123: replace strict_strtoul() with kstrtoul() Jingoo Han
2013-06-06 19:51 ` 'Greg Kroah-Hartman'
2013-06-07  0:57   ` Jingoo Han [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-06-07  1:00 Jingoo Han

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='002b01ce6319$ede58fa0$c9b0aee0$@samsung.com' \
    --to=jg1.han@samsung.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=arnd@arndb.de \
    --cc=eric.piel@tremplin-utc.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=holt@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.hennerich@analog.com \
    --cc=sivanich@sgi.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