From: Dave Martin <Dave.Martin@arm.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man <linux-man@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org,
Tim Chen <tim.c.chen@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v2 2/6] prctl.2: Add PR_SPEC_INDIRECT_BRANCH for SPECULATION_CTRL prctls
Date: Mon, 1 Jun 2020 14:51:13 +0100 [thread overview]
Message-ID: <20200601135112.GB5031@arm.com> (raw)
In-Reply-To: <CAKgNAkhwYASEM+wqaDZQ-ftcB3jnsVN2cXq4E_1ep1rqv+4aLw@mail.gmail.com>
On Thu, May 28, 2020 at 09:01:59AM +0200, Michael Kerrisk (man-pages) wrote:
> Hi Dave,
>
> On Wed, 27 May 2020 at 23:18, Dave Martin <Dave.Martin@arm.com> wrote:
> >
> > Add the PR_SPEC_INDIRECT_BRANCH "misfeature" added in Linux 4.20
> > for PR_SET_SPECULATION_CTRL and PR_GET_SPECULATION_CTRL.
> >
> > Signed-off-by: Dave Martin <Dave.Martin@arm.com>
> > Cc: Tim Chen <tim.c.chen@linux.intel.com>
> > Cc: Thomas Gleixner <tglx@linutronix.de>
>
> I had also applied this patch from the email you sent earlier. I've
> pushed those changes to master now.
Thanks for this.
Do you publish a "development" branch somewhere, or similar?
If possible, it's nice to have git rebase work out which patches to drop
for me rather than me doing it by hand.
Don't bother if publishing an extra branch doesn't fit with your
workflow, though.
Cheers
---Dave
next prev parent reply other threads:[~2020-06-01 13:51 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 21:17 [PATCH v2 0/6] prctl.2 man page updates for Linux 5.6 Dave Martin
2020-05-27 21:17 ` [PATCH v2 1/6] prctl.2: ffix use literal hyphens when referencing kernel docs Dave Martin
2020-05-28 6:05 ` Michael Kerrisk (man-pages)
2020-05-27 21:17 ` [PATCH v2 2/6] prctl.2: Add PR_SPEC_INDIRECT_BRANCH for SPECULATION_CTRL prctls Dave Martin
2020-05-28 7:01 ` Michael Kerrisk (man-pages)
2020-06-01 13:51 ` Dave Martin [this message]
2020-06-09 11:00 ` Michael Kerrisk (man-pages)
2020-05-27 21:17 ` [PATCH v2 3/6] prctl.2: Add PR_SPEC_DISABLE_NOEXEC " Dave Martin
2020-05-28 6:57 ` Michael Kerrisk (man-pages)
2020-05-28 13:45 ` Waiman Long
2020-05-27 21:17 ` [PATCH v2 4/6] prctl.2: Add SVE prctls (arm64) Dave Martin
2020-06-09 9:57 ` Will Deacon
2020-06-09 14:11 ` Dave Martin
2020-06-09 14:49 ` Will Deacon
2020-06-10 9:44 ` Dave Martin
2020-06-09 11:39 ` Michael Kerrisk (man-pages)
2020-06-10 9:45 ` Dave Martin
2020-05-27 21:17 ` [PATCH v2 5/6] prctl.2: Add PR_PAC_RESET_KEYS (arm64) Dave Martin
2020-06-09 10:02 ` Will Deacon
2020-06-09 11:03 ` Michael Kerrisk (man-pages)
2020-06-09 11:36 ` Michael Kerrisk (man-pages)
2020-06-09 14:16 ` Dave Martin
2020-06-09 18:11 ` Michael Kerrisk (man-pages)
2020-05-27 21:17 ` [RFC PATCH v2 6/6] prctl.2: Add tagged address ABI control prctls (arm64) Dave Martin
2020-06-09 11:04 ` Michael Kerrisk (man-pages)
2020-06-09 13:38 ` Will Deacon
2020-06-09 17:22 ` Catalin Marinas
2020-06-10 10:06 ` Dave Martin
2020-06-10 15:26 ` Catalin Marinas
2020-06-10 16:42 ` Dave Martin
2020-06-10 17:42 ` Catalin Marinas
2020-06-15 14:51 ` Dave Martin
2020-06-24 9:54 ` Michael Kerrisk (man-pages)
2020-06-24 10:29 ` Dave Martin
2020-05-28 7:11 ` [PATCH v2 0/6] prctl.2 man page updates for Linux 5.6 Michael Kerrisk (man-pages)
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=20200601135112.GB5031@arm.com \
--to=dave.martin@arm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.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).