From: Christoph Hellwig <hch@infradead.org>
To: Frank Sorenson <sorenson@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [nfs-utils PATCH] Replace non-thread-safe strtok function calls in gssd
Date: Thu, 9 Feb 2017 06:25:04 -0800 [thread overview]
Message-ID: <20170209142504.GA26900@infradead.org> (raw)
In-Reply-To: <6481e076-509a-1b60-bc46-7ac537ca24fe@redhat.com>
strtok_k is just as horrible as strtok, if you want to use a proper
API switch to strsep()
prev parent reply other threads:[~2017-02-09 14:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 13:10 [nfs-utils PATCH] Replace non-thread-safe strtok function calls in gssd Frank Sorenson
2017-02-09 14:25 ` Christoph Hellwig [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=20170209142504.GA26900@infradead.org \
--to=hch@infradead.org \
--cc=linux-nfs@vger.kernel.org \
--cc=sorenson@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;
as well as URLs for NNTP newsgroup(s).