[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 12 Dec 2017 12:51:05 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Will Deacon <will.deacon@....com>,
Dave Martin <Dave.Martin@....com>,
Philippe Ombredanne <pombredanne@...b.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] scripts/decodecode: Make it take multiline Code line
On Tue, 12 Dec 2017 12:03:23 +0200 Andy Shevchenko <andriy.shevchenko@...ux.intel.com> 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?
Powered by blists - more mailing lists