linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Borislav Petkov <bp@alien8.de>, "Moore, Robert" <robert.moore@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"devel@acpica.org" <devel@acpica.org>,
	"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
	"Box, David E" <david.e.box@intel.com>
Subject: Re: [PATCH] ACPICA / Interpreter: Remove redundant newline
Date: Fri, 09 Sep 2016 12:15:56 -0700	[thread overview]
Message-ID: <1473448556.10509.6.camel@perches.com> (raw)
In-Reply-To: <20160909190619.4hjrynq6trw4vw45@pd.tnic>

On Fri, 2016-09-09 at 21:06 +0200, Borislav Petkov wrote:
> Works for me. A lot of kernel code does stuff like that already:
> $ git grep -E "\(\"\\\n\"\)" | wc -l
> 1550

<shrug>  If you want.

and fyi:

Most of those are pr_cont uses for multiple printks to a single
output line terminations.


  reply	other threads:[~2016-09-09 19:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-09 16:12 [PATCH] ACPICA / Interpreter: Remove redundant newline Borislav Petkov
2016-09-09 18:26 ` Moore, Robert
2016-09-09 18:40   ` Borislav Petkov
2016-09-09 18:46     ` Moore, Robert
2016-09-09 18:50       ` Borislav Petkov
2016-09-09 18:55     ` Joe Perches
2016-09-14  3:14       ` Zheng, Lv
2016-09-09 18:45   ` Moore, Robert
2016-09-09 19:06     ` Borislav Petkov
2016-09-09 19:15       ` Joe Perches [this message]
2016-09-09 19:25         ` Borislav Petkov
2016-09-14  3:11     ` Zheng, Lv
2016-09-14 14:03       ` Moore, Robert
2016-09-14  3:09 ` Zheng, Lv
2016-09-14 11:30   ` Borislav Petkov
2016-09-19  9:30     ` Zheng, Lv
2016-09-19 10:12       ` Borislav Petkov
2016-09-23  6:46         ` [PATCH] acpiexec: Move an acpiexec specific purposed new line to acpiexec specific file Lv Zheng
2016-09-23  6:49         ` Lv Zheng

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=1473448556.10509.6.camel@perches.com \
    --to=joe@perches.com \
    --cc=bp@alien8.de \
    --cc=david.e.box@intel.com \
    --cc=devel@acpica.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=robert.moore@intel.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;
as well as URLs for NNTP newsgroup(s).