From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58391) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a9wca-0008Ui-9w for qemu-devel@nongnu.org; Fri, 18 Dec 2015 10:07:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a9wcX-0004AQ-33 for qemu-devel@nongnu.org; Fri, 18 Dec 2015 10:07:04 -0500 Received: from mx1.redhat.com ([209.132.183.28]:52857) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a9wcW-0004AK-Tl for qemu-devel@nongnu.org; Fri, 18 Dec 2015 10:07:01 -0500 From: Markus Armbruster References: <1449858642-24267-1-git-send-email-jjherne@linux.vnet.ibm.com> <87poy9rybu.fsf@blackfin.pond.sub.org> <566ED627.2030706@linux.vnet.ibm.com> <87mvtdnim6.fsf@blackfin.pond.sub.org> <5672F59B.7020907@linux.vnet.ibm.com> <87k2odszeo.fsf@blackfin.pond.sub.org> Date: Fri, 18 Dec 2015 16:06:58 +0100 In-Reply-To: <87k2odszeo.fsf@blackfin.pond.sub.org> (Markus Armbruster's message of "Thu, 17 Dec 2015 19:28:15 +0100") Message-ID: <8760zvbxt9.fsf@blackfin.pond.sub.org> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Qemu-devel] [PATCH v2] checkpatch: Detect newlines in error_report and other error functions List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Jason J. Herne" Cc: blauwirbel@gmail.com, cornelia.huck@de.ibm.com, qemu-devel@nongnu.org Markus Armbruster writes: > "Jason J. Herne" writes: > >> On 12/14/2015 10:40 AM, Markus Armbruster wrote: >>> "Jason J. Herne" writes: >>> >>>> On 12/14/2015 07:47 AM, Markus Armbruster wrote: >>>>> "Jason J. Herne" writes: >>>>> >>>>>> We don't want newlines embedded in error messages. This seems to >>>>>> be a common >>>>>> problem with new code so let's try to catch it with checkpatch. >>>>>> >>>>>> This will not catch cases where newlines are inserted into the >>>>>> middle of an >>>>>> existing multi-line statement. But those cases should be rare. >>>>>> >>>>>> Signed-off-by: Jason J. Herne >>>>> >> ... >>>> But I will take a look at this series and see if we can do better :). >>> >>> Thanks! If we can't, then I'm for taking this imperfect patch, because >>> flagging some of these mistakes is better than flagging none. >>> >>> >> >> I won't get a chance to get back to this before the new year. So feel >> free to push this (unless someone objects) and I'll see what I can do >> about improving it in January. > > Makes sense. Applied to my local error-next branch. With the warning changed from "Error function text should not contain newlines\n" to "Error message string should not contain newlines\n" [...]