From: james_p_freyensee@linux.intel.com (J Freyensee)
Subject: [PATCH v4] add u64 number parser
Date: Mon, 26 Sep 2016 17:42:39 -0700 [thread overview]
Message-ID: <1474936959.3078.20.camel@linux.intel.com> (raw)
In-Reply-To: <57e7f7cf.3jEpECHRn0rNlj8v%james.smart@broadcom.com>
On Sun, 2016-09-25@09:14 -0700, James Smart wrote:
> add u64 number parser
>
> Reverted back to version 2 of the patch.??This adds the interface
> using existing logic. Comments from the prior reviewers to move to
> kasprintf were rejected by Linus.
>
> Signed-off-by: James Smart <james.smart at broadcom.com>
Acked-by: Jay Freyensee <james_p_freyensee at linux.intel.com>
WARNING: multiple messages have this Message-ID (diff)
From: J Freyensee <james_p_freyensee@linux.intel.com>
To: James Smart <james.smart@broadcom.com>,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH v4] add u64 number parser
Date: Mon, 26 Sep 2016 17:42:39 -0700 [thread overview]
Message-ID: <1474936959.3078.20.camel@linux.intel.com> (raw)
In-Reply-To: <57e7f7cf.3jEpECHRn0rNlj8v%james.smart@broadcom.com>
On Sun, 2016-09-25 at 09:14 -0700, James Smart wrote:
> add u64 number parser
>
> Reverted back to version 2 of the patch. This adds the interface
> using existing logic. Comments from the prior reviewers to move to
> kasprintf were rejected by Linus.
>
> Signed-off-by: James Smart <james.smart@broadcom.com>
Acked-by: Jay Freyensee <james_p_freyensee@linux.intel.com>
next prev parent reply other threads:[~2016-09-27 0:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-25 16:14 [PATCH v4] add u64 number parser James Smart
2016-09-25 16:14 ` James Smart
2016-09-27 0:42 ` J Freyensee [this message]
2016-09-27 0:42 ` J Freyensee
-- strict thread matches above, loose matches on Subject: below --
2017-01-30 15:08 J. R. Okajima
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=1474936959.3078.20.camel@linux.intel.com \
--to=james_p_freyensee@linux.intel.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 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.