From: Jarkko Sakkinen <jarkko@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Kai Huang <kai.huang@intel.com>,
x86@kernel.org, linux-sgx@vger.kernel.org,
dave.hansen@linux.intel.com, dave.hansen@intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/sgx: Avoid returning NULL in __sgx_alloc_epc_page()
Date: Fri, 19 Mar 2021 17:22:56 +0200 [thread overview]
Message-ID: <YFTB0HD/4Hc0KvT3@kernel.org> (raw)
In-Reply-To: <20210319145931.GH6251@zn.tnic>
On Fri, Mar 19, 2021 at 03:59:31PM +0100, Borislav Petkov wrote:
> On Fri, Mar 19, 2021 at 04:50:33PM +0200, Jarkko Sakkinen wrote:
> > > > I was on the verge whether to merge that into the original patch since
> > > > it is the top patch on the branch or create a new one but opted for
> > > > former because this way it won't break bisection and people won't have
> > > > to pay attention whether there's a fix patch to the NUMA patch too, in
> > > > case they wanna backport and whatnot.
>
> ...
>
> > I understood Boris' comment that the fixes would not be squashed.
>
> Please read it again and let me know what about it is not clear. It is
> at the beginning of this mail.
I did misread it for the first time.
So let's sanity: you *are* going to squash the patches together because
that way it's factors easier to backport the whole thing?
Is this the correct understanding?
Fair point, I can cope with that.
> --
> Regards/Gruss,
> Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette
>
/Jarkko
next prev parent reply other threads:[~2021-03-19 15:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 4:06 [PATCH] x86/sgx: Avoid returning NULL in __sgx_alloc_epc_page() Kai Huang
2021-03-19 5:42 ` Jarkko Sakkinen
2021-03-19 8:45 ` Borislav Petkov
2021-03-19 9:01 ` Kai Huang
2021-03-19 9:12 ` Kai Huang
2021-03-19 14:50 ` Jarkko Sakkinen
2021-03-19 14:59 ` Borislav Petkov
2021-03-19 15:22 ` Jarkko Sakkinen [this message]
2021-03-19 15:52 ` Borislav Petkov
2021-03-19 15:59 ` Dave Hansen
2021-03-19 16:09 ` Borislav Petkov
2021-03-19 14:49 ` Jarkko Sakkinen
2021-03-19 18:45 ` [tip: x86/sgx] x86/sgx: Add a basic NUMA allocation scheme to sgx_alloc_epc_page() tip-bot2 for 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=YFTB0HD/4Hc0KvT3@kernel.org \
--to=jarkko@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=kai.huang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.