linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: linux-next: build failures after merge of the vfs tree
Date: Tue, 16 Jun 2020 10:34:40 +1000	[thread overview]
Message-ID: <20200616103440.35a80b4b@canb.auug.org.au> (raw)
In-Reply-To: <20200616103330.2df51a58@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 2469 bytes --]

[Just adding Herbert to cc]

On Tue, 16 Jun 2020 10:33:30 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
> 
> After merging the vfs tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
> 
> drivers/dma/uniphier-xdmac.c: In function 'uniphier_xdmac_prep_dma_memcpy':
> drivers/dma/uniphier-xdmac.c:293:7: error: implicit declaration of function 'kzalloc'; did you mean 'kvzalloc'? [-Werror=implicit-function-declaration]
>   293 |  xd = kzalloc(struct_size(xd, nodes, nr), GFP_NOWAIT);
>       |       ^~~~~~~
>       |       kvzalloc
> drivers/dma/uniphier-xdmac.c:293:5: warning: assignment to 'struct uniphier_xdmac_desc *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
>   293 |  xd = kzalloc(struct_size(xd, nodes, nr), GFP_NOWAIT);
>       |     ^
> drivers/dma/uniphier-xdmac.c: In function 'uniphier_xdmac_prep_slave_sg':
> drivers/dma/uniphier-xdmac.c:349:5: warning: assignment to 'struct uniphier_xdmac_desc *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
>   349 |  xd = kzalloc(struct_size(xd, nodes, sg_len), GFP_NOWAIT);
>       |     ^
> drivers/dma/uniphier-xdmac.c:373:4: error: implicit declaration of function 'kfree'; did you mean 'kvfree'? [-Werror=implicit-function-declaration]
>   373 |    kfree(xd);
>       |    ^~~~~
>       |    kvfree
> 
> Also, from the arm multi_v7_defconfig build:
> 
> drivers/dma/st_fdma.c: In function 'st_fdma_free_desc':
> drivers/dma/st_fdma.c:233:2: error: implicit declaration of function 'kfree'; did you mean 'vfree'? [-Werror=implicit-function-declaration]
>   233 |  kfree(fdesc);
>       |  ^~~~~
>       |  vfree
> drivers/dma/st_fdma.c: In function 'st_fdma_alloc_desc':
> drivers/dma/st_fdma.c:242:10: error: implicit declaration of function 'kzalloc'; did you mean 'vzalloc'? [-Werror=implicit-function-declaration]
>   242 |  fdesc = kzalloc(struct_size(fdesc, node, sg_len), GFP_NOWAIT);
>       |          ^~~~~~~
>       |          vzalloc
> drivers/dma/st_fdma.c:242:8: warning: assignment to 'struct st_fdma_desc *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
>   242 |  fdesc = kzalloc(struct_size(fdesc, node, sg_len), GFP_NOWAIT);
>       |        ^
> 
> Caused by commit
> 
>   f0187db056dc ("iov_iter: Move unnecessary inclusion of crypto/hash.h")
> 
> I have reverted that commit for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-06-16  0:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-16  0:33 linux-next: build failures after merge of the vfs tree Stephen Rothwell
2020-06-16  0:34 ` Stephen Rothwell [this message]
2020-06-16  1:05   ` Herbert Xu
2020-06-16  3:38     ` Al Viro
2020-06-16 14:38       ` Herbert Xu
2020-06-16 15:14         ` Al Viro
2020-06-17  6:57         ` Stephen Rothwell
2020-06-17  7:03           ` Herbert Xu
2020-06-17  7:31             ` Stephen Rothwell
2020-06-17  7:38               ` Herbert Xu
2020-06-18  0:08                 ` Stephen Rothwell
2020-06-30  1:58                   ` Stephen Rothwell
2020-06-30  2:14                     ` Herbert Xu
2020-06-30 13:36                       ` Al Viro
2020-06-17  8:06             ` 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=20200616103440.35a80b4b@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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).