linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
Cc: "sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"Hansen, Dave" <dave.hansen@intel.com>
Subject: Re: Shadow stack branch for linux-next
Date: Fri, 4 Aug 2023 21:07:30 +0100	[thread overview]
Message-ID: <15e8f5d0-4c64-475c-b095-5883d5af89b7@sirena.org.uk> (raw)
In-Reply-To: <5339bb88079f75a1e725ece7fc562938ba193169.camel@intel.com>

[-- Attachment #1: Type: text/plain, Size: 881 bytes --]

On Fri, Aug 04, 2023 at 08:00:43PM +0000, Edgecombe, Rick P wrote:

> The shadow stack branch in tip has not been included in linux-next. An
> updated version is here:
> https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/log/?h=x86/shstk

> Apologies if I'm missing some part of the process. Is there anything
> needed to make it acceptable for inclusion?

> The series hasn't changed much since the 6.4 based branch except a
> rebase and a few small patches on top. AFAIK, there is nothing gating
> submission for 6.6, so it would be nice to get it some linux-next
> exposure. Please let me know if I can do anything to facilitate this.

I think previously it was picked up in -next by virtue of being included
via the x86 part of the tip tree (which does make sense for an x86
architecture feature) - not sure how x86 and general tip processes
usually work here though.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2023-08-04 20:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04 20:00 Shadow stack branch for linux-next Edgecombe, Rick P
2023-08-04 20:07 ` Mark Brown [this message]
2023-08-04 21:05   ` Dave Hansen

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=15e8f5d0-4c64-475c-b095-5883d5af89b7@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=dave.hansen@intel.com \
    --cc=linux-next@vger.kernel.org \
    --cc=rick.p.edgecombe@intel.com \
    --cc=sfr@canb.auug.org.au \
    /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).