mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: YueHaibing <yuehaibing@huawei.com>
To: Randy Dunlap <rdunlap@infradead.org>, <linux-kernel@vger.kernel.org>
Cc: <akpm@linux-foundation.org>, <keescook@chromium.org>,
	<mawilcox@microsoft.com>, <kstewart@linuxfoundation.org>,
	<aryabinin@virtuozzo.com>, <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] lib/string.c: fix a typo in comment: 'iff' -->'if'
Date: Fri, 29 Jun 2018 11:44:51 +0800	[thread overview]
Message-ID: <22bb151b-d651-597b-21b6-0e6346ac32c9@huawei.com> (raw)
In-Reply-To: <a0b2a088-4887-e864-d211-bed0665a0b81@infradead.org>



On 2018/6/29 11:35, Randy Dunlap wrote:
> On 06/28/2018 08:33 PM, YueHaibing wrote:
>> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
>> ---
>>  lib/string.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> Hi,
> 
> This isn't a typo.  "iff" means "if and only if".

ok, my poor english, thank you.

> 
>> diff --git a/lib/string.c b/lib/string.c
>> index 2c0900a..23ed944 100644
>> --- a/lib/string.c
>> +++ b/lib/string.c
>> @@ -609,7 +609,7 @@ EXPORT_SYMBOL(strsep);
>>   * @s1: one string
>>   * @s2: another string
>>   *
>> - * This routine returns true iff two strings are equal, treating both
>> + * This routine returns true if two strings are equal, treating both
>>   * NUL and newline-then-NUL as equivalent string terminations.  It's
>>   * geared for use with sysfs input strings, which generally terminate
>>   * with newlines but are compared against values without newlines.
>>
> 
> 


  reply	other threads:[~2018-06-29  3:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-29  3:33 YueHaibing
2018-06-29  3:35 ` Randy Dunlap
2018-06-29  3:44   ` YueHaibing [this message]
2018-06-29 15:30     ` David Laight
2018-06-29 20:25       ` Andy Shevchenko

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=22bb151b-d651-597b-21b6-0e6346ac32c9@huawei.com \
    --to=yuehaibing@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=aryabinin@virtuozzo.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=keescook@chromium.org \
    --cc=kstewart@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mawilcox@microsoft.com \
    --cc=rdunlap@infradead.org \
    /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

all inboxes | Powered by JetHome®