From: Zhiquan Li <zhiquan1.li@intel.com>
To: Jarkko Sakkinen <jarkko@kernel.org>,
Kai Huang <kai.huang@intel.com>, "Du, Fan" <fan.du@intel.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"linux-sgx@vger.kernel.org" <linux-sgx@vger.kernel.org>,
"Luck, Tony" <tony.luck@intel.com>,
"Hansen, Dave" <dave.hansen@intel.com>,
"Zhang, Cathy" <cathy.zhang@intel.com>
Cc: "Christopherson,, Sean" <seanjc@google.com>
Subject: Re: [PATCH v3 0/3] x86/sgx: fine grained SGX MCA behavior
Date: Tue, 7 Jun 2022 15:02:51 +0800 [thread overview]
Message-ID: <0350d13c-0122-365d-11cb-eca004b411ca@intel.com> (raw)
In-Reply-To: <86eb19b512771098136e43fcdac95be8646357e4.camel@kernel.org>
On 2022/6/7 14:35, Jarkko Sakkinen wrote:
> Considering Zhiquan's series: all the patches have different message ID,
> which puts them into different threads and makes it hard to apply.
>
> E.g.
>
> https://lore.kernel.org/linux-sgx/20220525100625.760633-1-zhiquan1.li@intel.com/T/#u
>
> https://lore.kernel.org/linux-sgx/20220525100730.760815-1-zhiquan1.li@intel.com/T/#u
>
> Zhiquan: can you send your patch series as a single series? Easiest
> way to do it is to use git send-email. Right now the series broken.
Thanks for the heads up.
I was not aware of the patch series are broken on https://lore.kernel.org/.
I do use git send-email, there must be some settings are wrong,
let me check my git config.
Sorry for the inconvenience.
Best Regards,
Zhiquan
>
> BR, Jarkko
next prev parent reply other threads:[~2022-06-07 7:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 10:06 [PATCH v3 0/3] x86/sgx: fine grained SGX MCA behavior Zhiquan Li
2022-05-26 0:35 ` Jarkko Sakkinen
2022-06-03 1:15 ` Du, Fan
2022-06-06 10:40 ` Kai Huang
2022-06-07 6:35 ` Jarkko Sakkinen
2022-06-07 7:02 ` Zhiquan Li [this message]
2022-06-07 8:26 ` Jarkko Sakkinen
2022-06-07 15:43 ` Luck, Tony
2022-06-08 0:19 ` Jarkko Sakkinen
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=0350d13c-0122-365d-11cb-eca004b411ca@intel.com \
--to=zhiquan1.li@intel.com \
--cc=cathy.zhang@intel.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=fan.du@intel.com \
--cc=jarkko@kernel.org \
--cc=kai.huang@intel.com \
--cc=linux-sgx@vger.kernel.org \
--cc=seanjc@google.com \
--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