mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: 韦东辉 <weidonghui@allwinnertech.com>
Cc: akpm <akpm@linux-foundation.org>, maz <maz@misterjones.org>,
	will <will@kernel.org>, rabin <rabin@rab.in>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: Re:[PATCH v2] scripts/decodecode: fix faulting instruction no print when opps.file is DOS format
Date: Wed, 29 Sep 2021 11:44:17 +0200	[thread overview]
Message-ID: <YVQ1cSttGChXIZ5J@zn.tnic> (raw)
In-Reply-To: <17adc8ce-f6b0-4337-a62b-d9a39b000b56.weidonghui@allwinnertech.com>

On Wed, Sep 29, 2021 at 10:37:07AM +0800, 韦东辉 wrote:
> HI,all Thank you Borislav Petkov for helping me add the CC email
> list. I don't quite understand the meaning of this Google link
https://stackoverflow.com/questions/12167178/replace-windows-newlines-in-a-lot-of-files-using-sed-but-it-doesnt).

> This means that decodecode does not need to process CR(^M)? Must
> ensure that there is no CR(^M) when inputting log? If so, it will
> increase the cost of learning for others. And I think adding tr -d
> "\\015" will not destroy the beauty of the code, but enhance the
> compatibility of decodecode.

You don't need to use a different tool, tr in this case, to remove the
^M character - sed can do that just fine. And that link has the answer
how, I'll let you figure it out.

Also, please do not top-post when replying but put your reply *under*
the text you're replying to, just like I did.

Thx.

-- 
Regards/Gruss,
    Boris.

SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg

           reply	other threads:[~2021-09-29  9:44 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <17adc8ce-f6b0-4337-a62b-d9a39b000b56.weidonghui@allwinnertech.com>]

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=YVQ1cSttGChXIZ5J@zn.tnic \
    --to=bp@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@misterjones.org \
    --cc=rabin@rab.in \
    --cc=weidonghui@allwinnertech.com \
    --cc=will@kernel.org \
    /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

all inboxes | Powered by JetHome®