linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Linux Crypto List <linux-crypto@vger.kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the crypto tree
Date: Sun, 25 Aug 2019 20:01:24 +0200	[thread overview]
Message-ID: <ce5be2de-5e6c-b571-fffe-99888f7cf3a5@redhat.com> (raw)
In-Reply-To: <20190823131442.5a84a475@canb.auug.org.au>

Hi,

On 23-08-19 05:14, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the crypto tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
> 
> WARNING: modpost: missing MODULE_LICENSE() in lib/crypto/libsha256.o
> see include/linux/module.h for more information
> 
> Presumably introduced by commit
> 
>    01d3aee86625 ("crypto: sha256 - Make lib/crypto/sha256.c suitable for generic use")

Yeah my bad, I did not think about this getting build as a module.

I will submit a followup patch fixing this.

Regards,

Hans

  reply	other threads:[~2019-08-25 18:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-23  3:14 linux-next: build warning after merge of the crypto tree Stephen Rothwell
2019-08-25 18:01 ` Hans de Goede [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-12  3:48 Stephen Rothwell
2024-02-12 12:59 ` Cabiddu, Giovanni
2022-11-21  1:52 Stephen Rothwell
2022-07-11 10:49 Stephen Rothwell
2019-02-04  0:01 Stephen Rothwell
2018-10-05  5:31 Stephen Rothwell
2018-03-19  1:04 Stephen Rothwell
2018-03-19  5:44 ` Harsh Jain
2018-01-19  1:49 Stephen Rothwell
2018-01-19  4:21 ` Harsh Jain
2018-01-19  5:12   ` Herbert Xu
2017-07-31  2:17 Stephen Rothwell
2017-07-31 13:50 ` Gary R Hook
2016-08-25  1:38 Stephen Rothwell
2016-08-25  6:20 ` Martin Schwidefsky
2016-08-25  7:47   ` Herbert Xu
2016-08-25 11:14     ` Stephen Rothwell

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=ce5be2de-5e6c-b571-fffe-99888f7cf3a5@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).