mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Will Deacon <will.deacon@arm.com>,
	Dave Martin <Dave.Martin@arm.com>,
	Philippe Ombredanne <pombredanne@nexb.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] scripts/decodecode: Make it take multiline Code line
Date: Tue, 19 Dec 2017 14:54:55 -0800	[thread overview]
Message-ID: <20171219145455.a07f15f0e4d875a12dbe0875@linux-foundation.org> (raw)
In-Reply-To: <1513695919.7000.198.camel@linux.intel.com>

On Tue, 19 Dec 2017 17:05:19 +0200 Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:

> > That's rather hard to understand.  An example would help?
> 
> When you have a file out of oops the Code line looks like
> 
> Code: hh hh ... <hh> ... hh\n
> 
> When copy'n'paste from, for example, email where sender or some middle
> MTA split it, the line looks like:
> 
> Code: hh hh ... hh\n
> hh ... <hh> ... hh\n
> hh hh ... hh\n
> 
> The Code line followed by another oops line usually contains characters
> out of hex digit + space + < + > set. That's what second paragraph
> describes.

Oh, OK, yeah, that's irritating.  I thought we fixed it ages ago!

> Should I resend with information above included?

I updated the changelog, thanks.

      reply	other threads:[~2017-12-19 22:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-12 10:03 Andy Shevchenko
2017-12-12 20:51 ` Andrew Morton
2017-12-19 15:05   ` Andy Shevchenko
2017-12-19 22:54     ` Andrew Morton [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171219145455.a07f15f0e4d875a12dbe0875@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=Dave.Martin@arm.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pombredanne@nexb.com \
    --cc=will.deacon@arm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome