historical-speck.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: speck@linutronix.de
Subject: [MODERATED] Re: Slow Randomizing Boosts Denial of Service - Bulletin #2
Date: Tue, 05 May 2020 00:41:17 +0100	[thread overview]
Message-ID: <1d0c8741275d985ba070ad8ccdcf781abcc7c7a4.camel@decadent.org.uk> (raw)
In-Reply-To: <87wo5zobku.fsf@nanos.tec.linutronix.de>

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

On Tue, 2020-04-28 at 17:48 +0200, speck for Thomas Gleixner wrote:
> Folks!
> 
> I've merged the documentation update from Josh into the master branch of
> the speck git repository at:
> 
>    cvs.ou.linutronix.de:linux/speck/linux
> 
> The stable branches linux-5.6.y, linux-5.4.y, linux-4.19.y and
> linux-4.14.y have been updated as well.
> 
> The badly smelling linux-4.9.y and linux-4.4.y branches have the backports provided
> by Mark.
> 
> A tarball with git bundles is attached.

I noticed that the backports of "x86/cpu: Add a steppings field to
struct x86_cpu_id" to 5.4 and 5.6 add a couple of unused macros to the
top of <arch/x86/include/asm/cpu_device_id.h>:

+#define X86_CENTAUR_FAM6_C7_D          0xd
+#define X86_CENTAUR_FAM6_NANO          0xf

It looks like a bogus conflict resolution.  The backports to older
versions don't have these.

Ben.

-- 
Ben Hutchings
It's easier to fight for one's principles than to live up to them.


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-05-04 23:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28 15:48 Thomas Gleixner
2020-05-04 23:41 ` Ben Hutchings [this message]
2020-05-05 19:29 ` [MODERATED] " Borislav Petkov
2020-05-05 21:31   ` mark gross

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=1d0c8741275d985ba070ad8ccdcf781abcc7c7a4.camel@decadent.org.uk \
    --to=ben@decadent.org.uk \
    --cc=speck@linutronix.de \
    --subject='[MODERATED] Re: Slow Randomizing Boosts Denial of Service - Bulletin #2' \
    /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

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).