From: Borislav Petkov <bp@alien8.de>
To: Aili Yao <yaoaili@kingsoft.com>
Cc: <lenb@kernel.org>, <james.morse@arm.com>, <rjw@rjwysocki.net>,
<tony.luck@intel.com>, <linux-acpi@vger.kernel.org>,
<YANGFENG1@kingsoft.com>
Subject: Re: [PATCH] ACPI, APEI, Fix incorrect return value of apei_map_generic_address
Date: Thu, 12 Nov 2020 11:32:58 +0100 [thread overview]
Message-ID: <20201112103258.GA12908@nazgul.tnic> (raw)
In-Reply-To: <20201112181203.6c39d096.yaoaili@kingsoft.com>
On Thu, Nov 12, 2020 at 06:12:03PM +0800, Aili Yao wrote:
> If not this, please help point out!.
If there's something you're not clear on, searching the kernel tree
might help:
[ ~/kernel/linux> git grep top-post Documentation/
Documentation/process/2.Process.rst:444:- Avoid top-posting (the practice of putting your answer above the quoted
and now you open that document and read:
"- Avoid top-posting (the practice of putting your answer above the quoted
text you are responding to). It makes your response harder to read and
makes a poor impression."
Here's another example:
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
Also, read this:
http://daringfireball.net/2007/07/on_top
Also, you can look at mail threads on lkml to see how most people reply
to mail - that also gives a good example what to do.
I hope it is clear now.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-11-12 10:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e0e1cf62-6e49-1524-a370-41532c5b4ac7 () arm ! com>
2020-11-10 12:00 ` [PATCH] ACPI, APEI, Fix incorrect return value of apei_map_generic_address yaoaili126
2020-11-10 14:54 ` Borislav Petkov
2020-11-12 9:24 ` Aili Yao
2020-11-12 10:12 ` Aili Yao
2020-11-12 10:32 ` Borislav Petkov [this message]
2020-11-12 11:30 ` Aili Yao
[not found] <20201102023332.7638-1-yaoaili126 () 163 ! com>
2020-11-02 3:00 ` yaoaili126
[not found] <28dc453f-40b8-8263-5aeb-f8979f54a941 () arm ! com>
2020-11-02 2:33 ` yaoaili126
2020-11-02 2:47 ` yaoaili126
2020-11-03 17:11 ` Luck, Tony
2020-11-06 19:34 ` James Morse
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=20201112103258.GA12908@nazgul.tnic \
--to=bp@alien8.de \
--cc=YANGFENG1@kingsoft.com \
--cc=james.morse@arm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tony.luck@intel.com \
--cc=yaoaili@kingsoft.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