Historical speck list archives
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: speck@linutronix.de
Subject: [MODERATED] Re: The Annnoying Affair has No eXcuses - Bulletin #4
Date: Thu, 14 Nov 2019 14:12:18 +0800	[thread overview]
Message-ID: <20191114061218.GA424694@kroah.com> (raw)
In-Reply-To: <cb8cda1f86bf723e846317352551cbcb195d3637.camel@decadent.org.uk>

On Sat, Nov 09, 2019 at 10:39:53PM +0000, speck for Ben Hutchings wrote:
> On Thu, 2019-11-07 at 21:17 +0100, speck for Thomas Gleixner wrote:
> > Folks,
> > 
> > I've picked up Paolos backports and updated the stable branches
> > linux-5.3.y, linux-4.19.y and linix-4.14.y, which also have been rebased to
> > the latest stable versions.
> > 
> > The changes are available as usual from:
> > 
> >   cvs.ou.linutronix.de:linux/speck/linux  
> > 
> > Git bundles for the linux-5.3.y, linux-4.19.y and linix-4.14.y branches
> > against their upstream versions are attached.
> 
> Here's my backport to 4.9.  I've tested the NX fixes for a while, but
> don't have any hardware to test the TAA fixes on.

I don't know what you based this on, I can't seem to pull from it:

error: inflate: data stream error (invalid distance too far back)
fatal: pack has bad object at offset 20842: inflate returned -3
error: index-pack died

Same thing for the 4.4 bundle:

error: inflate: data stream error (invalid distance too far back)
fatal: pack has bad object at offset 12348: inflate returned -3
error: index-pack died

Can you send both of these as a tarball of patches or some other format
I can use?

thanks,

greg k-h

      parent reply	other threads:[~2019-11-14  6:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-07 20:17 The Annnoying Affair has No eXcuses - Bulletin #4 Thomas Gleixner
2019-11-08 10:35 ` [MODERATED] " Greg KH
2019-11-09 19:59 ` Ben Hutchings
2019-11-09 20:04   ` Ben Hutchings
2019-11-11 11:27   ` Thomas Gleixner
2019-11-11 13:03     ` [MODERATED] " Paolo Bonzini
2019-11-11 15:41       ` Thomas Gleixner
2019-11-09 22:39 ` [MODERATED] " Ben Hutchings
2019-11-09 23:57   ` Ben Hutchings
2019-11-10  0:30     ` Ben Hutchings
2019-11-11 17:22   ` mark gross
2019-11-11 19:03     ` mark gross
2019-11-12  2:26   ` Pawan Gupta
2019-11-14  6:12   ` Greg KH [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=20191114061218.GA424694@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=speck@linutronix.de \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).