From: Greg KH <greg@kroah.com>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: Luuk Paulussen <luuk.paulussen@alliedtelesis.co.nz>,
Jan Stancek <jstancek@redhat.com>,
stable@vger.kernel.org, Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [linux main PATCH] crypto: qat - make qat_asym_algs.o depend on asn1 headers
Date: Fri, 28 Sep 2018 06:45:55 +0200 [thread overview]
Message-ID: <20180928044555.GB20540@kroah.com> (raw)
In-Reply-To: <20180927224244.24591-1-chris.packham@alliedtelesis.co.nz>
On Fri, Sep 28, 2018 at 10:42:44AM +1200, Chris Packham wrote:
> From: Jan Stancek <jstancek@redhat.com>
>
> Parallel build can sporadically fail because asn1 headers may
> not be built yet by the time qat_asym_algs.o is compiled:
> drivers/crypto/qat/qat_common/qat_asym_algs.c:55:32: fatal error: qat_rsapubkey-asn1.h: No such file or directory
> #include "qat_rsapubkey-asn1.h"
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Jan Stancek <jstancek@redhat.com>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
>
> [upstream commit 81dc0365cfa7bc7c08a0e44d9ee04964df782e19]
> Reviewed-by: Scott Parlane <scott.parlane@alliedtelesis.co.nz>
> Reviewed-by: Luuk Paulussen <luuk.paulussen@alliedtelesis.co.nz>
>
> Change-Id: Ie811cd1fbb497c84ca86d18ae8362973c600d9a1
Why is this change-id line here? What am I supposed to do with this
patch overall? What stable tree do you want it in? It's already
backported to really old kernels today, shouldn't you just be using them
already?
confused,
greg k-h
next prev parent reply other threads:[~2018-09-28 11:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 22:42 [linux main PATCH] crypto: qat - make qat_asym_algs.o depend on asn1 headers Chris Packham
2018-09-28 4:45 ` Greg KH [this message]
2018-09-28 4:51 ` Chris Packham
2018-09-28 4:56 ` Greg KH
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=20180928044555.GB20540@kroah.com \
--to=greg@kroah.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=herbert@gondor.apana.org.au \
--cc=jstancek@redhat.com \
--cc=luuk.paulussen@alliedtelesis.co.nz \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.