From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: backports@vger.kernel.org
Subject: Re: [PATCH 1/4] patches: update crypto-ccm.patch for v4.11-rc1
Date: Fri, 10 Mar 2017 07:34:32 +0100 [thread overview]
Message-ID: <1489127672.3038.0.camel@sipsolutions.net> (raw)
In-Reply-To: <1489064253-3652-2-git-send-email-arend.vanspriel@broadcom.com> (sfid-20170309_140610_645275_5055B3F1)
On Thu, 2017-03-09 at 12:57 +0000, Arend van Spriel wrote:
> Since v4.11-rc1 the patch file for crypto/ccm.c, which is
> incorporated
> in the compat module, no longer applies. Update the patch file to fix
> the issue.
I think I want to get rid of this ccm thing entirely, any objections?
As I remember, it doesn't actually work properly anyway.
I suspect that if we really can't do anything else, we'd have to
provide a backport for all of crypto/, but I don't want to go there and
would rather mandate that all the crypto things are enabled in the base
kernel.
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2017-03-10 6:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 12:57 [PATCH 0/4] backports: fixes for wireless-testing Arend van Spriel
2017-03-09 12:57 ` [PATCH 1/4] patches: update crypto-ccm.patch for v4.11-rc1 Arend van Spriel
2017-03-10 6:34 ` Johannes Berg [this message]
2017-03-10 9:49 ` Arend Van Spriel
2017-03-10 9:52 ` Johannes Berg
2017-03-10 10:08 ` Arend Van Spriel
2017-03-10 10:09 ` Johannes Berg
2017-03-09 12:57 ` [PATCH 2/4] backports: add backport for idr_remove Arend van Spriel
2017-03-09 12:57 ` [PATCH 3/4] backports: introduce new definition for DECLARE_EWMA macro Arend van Spriel
2017-03-10 6:36 ` Johannes Berg
2017-03-10 9:53 ` Arend Van Spriel
2017-03-14 13:49 ` Johannes Berg
2017-03-09 12:57 ` [PATCH 4/4] backports: add dummy include/linux/sched/signal.h Arend van Spriel
2017-03-31 7:29 ` [PATCH 0/4] backports: fixes for wireless-testing Johannes Berg
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=1489127672.3038.0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.com \
--cc=backports@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.