From: Jarkko Sakkinen <jarkko@kernel.org>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Haitao Huang <haitao.huang@linux.intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
linux-sgx@vger.kernel.org, reinette.chatre@intel.com,
Borislav Petkov <bp@alien8.de>, Tony Luck <tony.luck@intel.com>
Subject: Re: [PATCH] selftests/sgx: retry the ioctls returned with EAGAIN
Date: Thu, 25 Aug 2022 08:39:12 +0300 [thread overview]
Message-ID: <YwcLAMB0HGHUU4bx@kernel.org> (raw)
In-Reply-To: <Ywb9qg9Ij+VCaG5v@kernel.org>
On Thu, Aug 25, 2022 at 07:42:18AM +0300, Jarkko Sakkinen wrote:
> On Mon, Aug 22, 2022 at 04:24:50PM -0700, Dave Hansen wrote:
> > On 8/16/22 07:24, Jarkko Sakkinen wrote:
> > > Dave, in addition to [*], these should be picked x86 tree for v6.0
> > >
> > > https://lore.kernel.org/linux-sgx/20220815233900.11225-1-jarkko@kernel.org/T/#t
> >
> > Was there an ack somewhere in that thread that I missed?
>
> Yes, both had mine.
>
> I sent both unmodified bundled into a single patch set, except cosmetic
> changes to the commit message. The discussion that followed up came up a
> day later I've send that response.
>
> The next version will be lacking ack's, given that I'm modifying the
> patches, i.e. will be disqualified to review them.
Also, the next version will include additional patch for
a bpftrace script derived from what I tossed with Haitao
in order to root cause the error. Probably useful to have
available, as it did the trick.
BR, Jarkko
prev parent reply other threads:[~2022-08-25 5:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 20:13 [PATCH] selftests/sgx: retry the ioctls returned with EAGAIN Haitao Huang
2022-08-14 19:39 ` Jarkko Sakkinen
2022-08-16 5:16 ` Haitao Huang
2022-08-16 14:24 ` Jarkko Sakkinen
2022-08-22 23:24 ` Dave Hansen
2022-08-25 4:42 ` Jarkko Sakkinen
2022-08-25 5:39 ` Jarkko Sakkinen [this message]
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=YwcLAMB0HGHUU4bx@kernel.org \
--to=jarkko@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=haitao.huang@linux.intel.com \
--cc=linux-sgx@vger.kernel.org \
--cc=reinette.chatre@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).