All of lore.kernel.org
 help / color / mirror / Atom feed
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 10:52:35 +0100	[thread overview]
Message-ID: <1489139555.3038.4.camel@sipsolutions.net> (raw)
In-Reply-To: <b5a13b6c-6ed7-7682-2043-1dcc8ddfec79@broadcom.com> (sfid-20170310_104945_709577_B870A5E9)

On Fri, 2017-03-10 at 10:49 +0100, Arend Van Spriel wrote:
> 
> On 10-3-2017 7:34, Johannes Berg wrote:
> > 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.
> 
> No objection here. Does the same apply to skcipher stuff?

I think so, but not sure.

> > 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.
> 
> But that can only work when crypto api in base kernel and backport
> kernel are the same, right?

No, I meant adding all of crypto/ to copy-list and making sure *that*
works across kernels ...

johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in

  reply	other threads:[~2017-03-10  9:52 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
2017-03-10  9:49     ` Arend Van Spriel
2017-03-10  9:52       ` Johannes Berg [this message]
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=1489139555.3038.4.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.