[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180607083856.ealw62v3wx43zeqz@vireshk-i7>
Date: Thu, 7 Jun 2018 14:08:56 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: "Du, Changbin" <changbin.du@...el.com>
Cc: Steven Rostedt <rostedt@...dmis.org>, gregkh@...uxfoundation.org,
alex.elder@...aro.org, Johan Hovold <johan@...nel.org>,
kbuild test robot <lkp@...el.com>,
linux-arch@...r.kernel.org, michal.lkml@...kovi.net,
linux-kernel@...r.kernel.org, arnd@...db.de,
yamada.masahiro@...ionext.com, lgirdwood@...il.com,
broonie@...nel.org, rdunlap@...radead.org, x86@...nel.org,
linux@...linux.org.uk, linux-sparse@...r.kernel.org,
mingo@...hat.com, kbuild-all@...org, akpm@...ux-foundation.org,
changbin.du@...il.com, tglx@...utronix.de,
linux-kbuild@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v5 2/4] kernel hacking: new config NO_AUTO_INLINE to
disable compiler auto-inline optimizations
On 07-06-18, 15:46, Du, Changbin wrote:
> I think if the destination is not a null terminated string (If I understand your
> description below), memcpy can be used to get rid of such warning. The warning
> makes sense in general as explained in mannual. Thanks!
The destination should be a null terminated string eventually, but we first need
to make sure src is a null terminated string.
--
viresh
Powered by blists - more mailing lists