From: Borislav Petkov <bp@alien8.de>
To: "Moore, Robert" <robert.moore@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Zheng, Lv" <lv.zheng@intel.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
Len Brown <lenb@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"devel@acpica.org" <devel@acpica.org>
Subject: Re: [PATCH] ACPICA / Interpreter: Remove redundant newline
Date: Fri, 9 Sep 2016 20:40:42 +0200 [thread overview]
Message-ID: <20160909184042.srv6jrio6s5umear@pd.tnic> (raw)
In-Reply-To: <94F2FBAB4432B54E8AACC7DFDE6C92E37E4F34B4@ORSMSX110.amr.corp.intel.com>
On Fri, Sep 09, 2016 at 06:26:17PM +0000, Moore, Robert wrote:
> Is this a big deal?
>
> We do this on purpose for AcpiExec, to make the screen output more readable.
Please do not top-post.
What do you mean "big deal"? All other ACPI_INFO calls don't have a "\n"
at the end except this one. How does one "\n" make some output more
readable?
(Btw, I have no idea what AcpiExec is. Grepping the kernel tree doesn't
give any results).
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2016-09-09 18:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 16:12 Borislav Petkov
2016-09-09 18:26 ` Moore, Robert
2016-09-09 18:40 ` Borislav Petkov [this message]
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
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=20160909184042.srv6jrio6s5umear@pd.tnic \
--to=bp@alien8.de \
--cc=devel@acpica.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.zheng@intel.com \
--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
all inboxes | Powered by JetHome®