All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Luca Coelho <luca@coelho.fi>, backports@vger.kernel.org
Subject: Re: [PATCH] backports: remove CRYPTO_CCM backport
Date: Thu, 19 Oct 2017 08:41:00 +0200	[thread overview]
Message-ID: <1508395260.8801.0.camel@sipsolutions.net> (raw)
In-Reply-To: <1508391450.5497.177.camel@coelho.fi>

On Thu, 2017-10-19 at 08:37 +0300, Luca Coelho wrote:
> 
> Should backports then depend on CRYPTO_CCM? It didn't really work in
> the past and I got a few reports of broken backport with old kernels
> due to missing CRYPTO_CCM in the kernel config.

this change will automatically make mac80211 depend on it, after re-
generation.

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

  reply	other threads:[~2017-10-19  6:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-13 10:31 [PATCH] backports: remove CRYPTO_CCM backport Johannes Berg
2017-10-19  5:37 ` Luca Coelho
2017-10-19  6:41   ` Johannes Berg [this message]
2017-10-19  8:50     ` Arend van Spriel
  -- strict thread matches above, loose matches on Subject: below --
2017-10-13 10:28 Johannes Berg
2017-10-13 10:32 ` 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=1508395260.8801.0.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=backports@vger.kernel.org \
    --cc=luca@coelho.fi \
    /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.