From: Aili Yao <yaoaili@kingsoft.com>
To: Borislav Petkov <bp@alien8.de>, <lenb@kernel.org>
Cc: <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 18:12:03 +0800 [thread overview]
Message-ID: <20201112181203.6c39d096.yaoaili@kingsoft.com> (raw)
In-Reply-To: <20201112172407.432b88cc.yaoaili@kingsoft.com>
Oh, Do you mean the document Posting.rst?
Is the wrong doing BUILD error from robot?
I am really sorry for this!
Before submit anything, I will do more build test and real test.
I will try my best not doing it again.
If not this, please help point out!.
Thank you!
On Thu, 12 Nov 2020 17:24:07 +0800
Aili Yao <yaoaili@kingsoft.com> wrote:
> Hi, Thanks for your reply!
> I am really sorry for the chaos from me!
>
>
> On Tue, 10 Nov 2020 15:54:50 +0100
> Borislav Petkov <bp@alien8.de> wrote:
>
> > On Tue, Nov 10, 2020 at 04:00:02AM -0800, yaoaili126@163.com wrote:
> > > From: Aili Yao <yaoaili@kingsoft.com>
> > >
> > > Hi!
> > > Thank you for all the suggestions and comments!
> > > I have re-submited the patch following your comments
> > > I really need to read Documentation/process more detailly!
> >
> > Yes, and while doing that please read about top-posting too and stop
> > doing it.
> I am sorry I don't fully get it, please help point it out and I will avoid
> doing it again.
> 1.The top-posting is the Documents in Documentation/ ?
> 2.I am sorry for the wrong doings, Can you be more clearly.
> Then I will avoid doing it.
>
> >
> > Thanks!
> >
>
> Thanks
> Aili Yao
next prev parent reply other threads:[~2020-11-12 10:12 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 [this message]
2020-11-12 10:32 ` Borislav Petkov
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=20201112181203.6c39d096.yaoaili@kingsoft.com \
--to=yaoaili@kingsoft.com \
--cc=YANGFENG1@kingsoft.com \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tony.luck@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