From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: Peter Huewe <PeterHuewe@gmx.de>,
"backports@vger.kernel.org" <backports@vger.kernel.org>
Subject: Re: Re: gentree fails at no such file compat/crypto-skcipher.c
Date: Wed, 10 Aug 2016 00:15:06 +0200 [thread overview]
Message-ID: <20160809221506.GG3296@wotan.suse.de> (raw)
In-Reply-To: <20160809212848.GF3296@wotan.suse.de>
On Tue, Aug 09, 2016 at 11:28:48PM +0200, Luis R. Rodriguez wrote:
> On Tue, Aug 09, 2016 at 07:02:51AM +0200, Peter Huewe wrote:
> If you can
> export the functionality as modular then you are set, as you can then
> just carry it as a new generic module helper. We have some of these,
> refer to tons of functionality in the directory backport/compat/
> in that take note of the Makefile
>
> compat-$(CPTCFG_BPAUTO_BUILD_CRYPTO_CCM) += crypto-ccm.o
> compat-$(CPTCFG_BPAUTO_CRYPTO_SKCIPHER) += crypto-skcipher.o
>
> We copy over from upstream crypto-ccm and throw it in here to
> provide our own copy. Additionally there is also patch for
> it, see patches/backport-adjustments/crypto-ccm.patch
>
> So the BPAUTO stuff is one of the auto-things we have.
I forgot to refer you also to the c-file trick used to copy
code for this purpose refer to backport/compat/Kconfig:
config BPAUTO_BUILD_CRYPTO_CCM
bool
default n if CRYPTO_CCM
default y if BPAUTO_CRYPTO_CCM
#c-file crypto/ccm.c
That c-file entry means copy upstream's copy to compat/
Luis
--
To unsubscribe from this list: send the line "unsubscribe backports" in
prev parent reply other threads:[~2016-08-09 22:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 7:52 gentree fails at no such file compat/crypto-skcipher.c Peter Huewe
2016-08-08 17:35 ` Luis R. Rodriguez
2016-08-08 19:05 ` Peter Huewe
2016-08-08 20:14 ` Luis R. Rodriguez
2016-08-09 5:02 ` Aw: " Peter Huewe
2016-08-09 21:28 ` Luis R. Rodriguez
2016-08-09 22:15 ` Luis R. Rodriguez [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=20160809221506.GG3296@wotan.suse.de \
--to=mcgrof@kernel.org \
--cc=PeterHuewe@gmx.de \
--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.