LKML Archive on
help / color / mirror / Atom feed
From: Matthew Wilcox <>
To: Andy Shevchenko <>
	Andrew Morton <>
Subject: Re: [PATCH v1 1/1] mm/util: Rephrase documentation for kmemdup_nul() to clarify input
Date: Mon, 19 Jul 2021 13:44:22 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, Jul 19, 2021 at 03:20:02PM +0300, Andy Shevchenko wrote:
> kmemdup_nul() strictly speaking is not related to the string API,
> while being quite useful for it. Rephrase documentation to make it
> clear that input data can be anything (any data, which may contain
> any bytes, including 0x00).

That's not a useful thing to do, though.  This rephrasing you've
done is more confusing than the original.

  reply	other threads:[~2021-07-19 12:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19 12:20 Andy Shevchenko
2021-07-19 12:44 ` Matthew Wilcox [this message]
2021-07-19 12:57   ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \
    --subject='Re: [PATCH v1 1/1] mm/util: Rephrase documentation for kmemdup_nul() to clarify input' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).