Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Mon, 19 Jul 2021 15:57:03 +0300
From:   Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To:     Matthew Wilcox <willy@infradead.org>
Cc:     linux-mm@kvack.org, linux-kernel@vger.kernel.org,
        Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v1 1/1] mm/util: Rephrase documentation for kmemdup_nul()
 to clarify input
Message-ID: <YPV2n6g0j1tkxF7M@smile.fi.intel.com>
References: <20210719122002.41334-1-andriy.shevchenko@linux.intel.com>
 <YPVzptA7JYMyWszg@casper.infradead.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <YPVzptA7JYMyWszg@casper.infradead.org>
Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
Precedence: bulk

On Mon, Jul 19, 2021 at 01:44:22PM +0100, Matthew Wilcox wrote:
> 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.

Okay, then drop it. Sorry for the noise.

-- 
With Best Regards,
Andy Shevchenko