From: "H.J. Lu" <hjl.tools@gmail.com>
To: Mayshao-oc <Mayshao-oc@zhaoxin.com>
Cc: "Carlos O'Donell" <carlos@redhat.com>,
Florian Weimer <fw@deneb.enyo.de>,
GNU C Library <libc-alpha@sourceware.org>,
"Qiyuan Wang(BJ-RD)" <QiyuanWang@zhaoxin.com>,
"Herry Yang(BJ-RD)" <HerryYang@zhaoxin.com>,
"Cooper Yan(BJ-RD)" <CooperYan@zhaoxin.com>,
"Ricky Li(BJ-RD)" <RickyLi@zhaoxin.com>
Subject: Re: [PATCH v3 2/3] x86: Add cache information support for Zhaoxin processors
Date: Thu, 30 Apr 2020 05:52:13 -0700 [thread overview]
Message-ID: <CAMe9rOqig8cPgiAnsTyfuPkZ3CS+CHe8CJxAvGJP6L+3KwiASQ@mail.gmail.com> (raw)
In-Reply-To: <2bd2c586658340a88e018b39f0a2771e@zhaoxin.com>
On Wed, Apr 29, 2020 at 11:04 PM Mayshao-oc <Mayshao-oc@zhaoxin.com> wrote:
>
>
> On Thur, April 30, 2020 at 1:16 PM H.J. Lu <hjl.tools@gmail.com> wrote:
> >
> > On Wed, Apr 29, 2020 at 10:10 PM Mayshao-oc <Mayshao-oc@zhaoxin.com>
> > wrote:
> > >
> > > Hi
> > >
> > > This is my first patch. I’m not sure what I need to do next about this patch
> > set.
> > > And I was wandering if this patch set is ok for the master.
> > >
> > > Thank you all for your patience and kind help.
> > >
> >
> > It is OK. Please check it in.
> >
> Do you mean that I should push the patch set to the master by myself?
> If so, I should have no permission to push. Would you like to push to the master
> for me at your leisure?
>
> If I understand something wrong, please feel free to point it out.
>
> Thank you very much.
Please send me those patches from "git format-patch" as attachments, I will
apply them for you.
--
H.J.
next prev parent reply other threads:[~2020-04-30 12:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 12:29 [PATCH v3 0/3] x86: Add " mayshao-oc
2020-04-24 12:29 ` [PATCH v3 1/3] x86: Add CPU Vendor ID detection " mayshao-oc
2020-04-24 12:53 ` H.J. Lu
2020-04-24 12:29 ` [PATCH v3 2/3] x86: Add cache information " mayshao-oc
2020-04-24 12:53 ` H.J. Lu
2020-04-26 5:54 ` Mayshao-oc
2020-04-26 12:07 ` H.J. Lu
2020-04-30 5:09 ` Mayshao-oc
2020-04-30 5:15 ` H.J. Lu
2020-04-30 6:04 ` Mayshao-oc
2020-04-30 12:52 ` H.J. Lu [this message]
2020-04-30 13:22 ` Mayshao-oc
2020-04-30 13:55 ` H.J. Lu
2020-04-30 14:39 ` Mayshao-oc
2020-04-30 19:10 ` Joseph Myers
2020-04-30 19:16 ` Florian Weimer
2020-04-30 19:21 ` H.J. Lu
2020-04-30 20:04 ` Florian Weimer
2020-04-24 12:29 ` [PATCH v3 3/3] x86: Add the test case of __get_cpu_features " mayshao-oc
2020-04-24 12:54 ` H.J. Lu
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=CAMe9rOqig8cPgiAnsTyfuPkZ3CS+CHe8CJxAvGJP6L+3KwiASQ@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=CooperYan@zhaoxin.com \
--cc=HerryYang@zhaoxin.com \
--cc=Mayshao-oc@zhaoxin.com \
--cc=QiyuanWang@zhaoxin.com \
--cc=RickyLi@zhaoxin.com \
--cc=carlos@redhat.com \
--cc=fw@deneb.enyo.de \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).