mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Stephan Müller" <smueller@chronox.de>
To: Tobias Regnery <tobias.regnery@gmail.com>
Cc: dhowells@redhat.com, james.l.morris@oracle.com, serge@hallyn.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KEYS: fix build failure with CONFIG_KEY_DH_OPERATIONS
Date: Tue, 11 Apr 2017 15:47:03 +0200	[thread overview]
Message-ID: <1508551.vSOrWJWSeP@tauon.chronox.de> (raw)
In-Reply-To: <20170411124512.23627-1-tobias.regnery@gmail.com>

Am Dienstag, 11. April 2017, 14:45:12 CEST schrieb Tobias Regnery:

Hi Tobias,

> With CONFIG_KEY_DH_OPERATIONS=y and CONFIG_CRYPTO=m we get the following
> link error:

Thanks for the patch. I just released the very same patch :-)

David, I guess it makes more sense now to simply apply that patch instead of 
me going back and update the original patch.

Thanks.

Ciao
Stephan

      reply	other threads:[~2017-04-11 13:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-11 12:45 Tobias Regnery
2017-04-11 13:47 ` Stephan Müller [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=1508551.vSOrWJWSeP@tauon.chronox.de \
    --to=smueller@chronox.de \
    --cc=dhowells@redhat.com \
    --cc=james.l.morris@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=serge@hallyn.com \
    --cc=tobias.regnery@gmail.com \
    /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
all inboxes | Powered by JetHome®