linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kai Huang <kai.huang@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Jarkko Sakkinen <jarkko@kernel.org>,
	linux-sgx@vger.kernel.org, x86@kernel.org,
	linux-kernel@vger.kernel.org, seanjc@google.com,
	dave.hansen@intel.com, tglx@linutronix.de, mingo@redhat.com,
	Yang Zhong <yang.zhong@intel.com>
Subject: Re: [PATCH v2] x86/sgx: Add missing xa_destroy() when virtual EPC is destroyed
Date: Sat, 26 Jun 2021 11:06:23 +1200	[thread overview]
Message-ID: <2be5bb5342ae568c198d61f5e8a8b4515b61ba66.camel@intel.com> (raw)
In-Reply-To: <YNXej3ru9kxQugvR@zn.tnic>

On Fri, 2021-06-25 at 15:47 +0200, Borislav Petkov wrote:
> On Sat, Jun 26, 2021 at 12:04:53AM +1200, Kai Huang wrote:
> > Oh sorry I thought the patch would go via x86/sgx branch
> 
> We usually send fixes through tip's urgent branches because they go
> straight to Linus and not wait for the merge window.
> 
> > and I didn't monitor the tip-bot2 mail which was moved to my local x86
> > folder.
> 
> That's not optimal because those tip-bot notifications are *exactly* for
> that - to let the involved parties know that the patch has been queued.
> 

Got it. Thanks for remaindering.


      reply	other threads:[~2021-06-25 23:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-16  0:36 [PATCH v2] x86/sgx: Add missing xa_destroy() when virtual EPC is destroyed Kai Huang
2021-06-23 13:28 ` Jarkko Sakkinen
2021-06-25  1:45   ` Kai Huang
2021-06-25  8:22     ` Borislav Petkov
2021-06-25 12:04       ` Kai Huang
2021-06-25 13:47         ` Borislav Petkov
2021-06-25 23:06           ` Kai Huang [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=2be5bb5342ae568c198d61f5e8a8b4515b61ba66.camel@intel.com \
    --to=kai.huang@intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@intel.com \
    --cc=jarkko@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sgx@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=seanjc@google.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=yang.zhong@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 NNTP newsgroup(s).