From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752546AbdLLUvL (ORCPT ); Tue, 12 Dec 2017 15:51:11 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:47264 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752425AbdLLUvH (ORCPT ); Tue, 12 Dec 2017 15:51:07 -0500 Date: Tue, 12 Dec 2017 12:51:05 -0800 From: Andrew Morton To: Andy Shevchenko Cc: Will Deacon , Dave Martin , Philippe Ombredanne , linux-kernel@vger.kernel.org Subject: Re: [PATCH v1] scripts/decodecode: Make it take multiline Code line Message-Id: <20171212125105.2ad43a65f42a63cc6e4f4bcb@linux-foundation.org> In-Reply-To: <20171212100323.33201-1-andriy.shevchenko@linux.intel.com> References: <20171212100323.33201-1-andriy.shevchenko@linux.intel.com> X-Mailer: Sylpheed 3.4.1 (GTK+ 2.24.23; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 12 Dec 2017 12:03:23 +0200 Andy Shevchenko wrote: > In case of running scripts/decodecode without any parameters in order to give a > copy'n'pasted Code line from, for example, email it would parse only first line > of it, while in emails it's split to few. > > So, add a logic to join this split back if and only if the following lines have > hex digits, or spaces, or '<', or '>' characters. It will be quite unlikely to > have a broken input in well formed Oops or dmesg, thus a simple regex is being > used. That's rather hard to understand. An example would help?