All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dave Airlie <airlied@linux.ie>, DRI <dri-devel@lists.freedesktop.org>
Cc: Thomas Zimmermann <tzimmermann@suse.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the drm tree
Date: Mon, 16 Nov 2020 10:44:44 +1100	[thread overview]
Message-ID: <20201116104444.044486ea@canb.auug.org.au> (raw)
In-Reply-To: <20201105175031.00e0b081@canb.auug.org.au>

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

Hi all,

On Thu, 5 Nov 2020 17:50:31 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
> 
> After merging the drm tree, today's linux-next build (htmldocs) produced
> these warnings:
> 
> include/linux/dma-buf-map.h:106: warning: Excess function parameter 'vaddr' description in 'DMA_BUF_MAP_INIT_VADDR'
> include/linux/dma-buf-map.h:106: warning: Function parameter or member 'vaddr_' not described in 'DMA_BUF_MAP_INIT_VADDR'
> include/linux/dma-buf-map.h:106: warning: Excess function parameter 'vaddr' description in 'DMA_BUF_MAP_INIT_VADDR'
> 
> Introduced by commit
> 
>   20e76f1a7059 ("dma-buf: Use struct dma_buf_map in dma_buf_vunmap() interfaces")

I am still getting these warnings.

-- 
Cheers,
Stephen Rothwell

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

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dave Airlie <airlied@linux.ie>, DRI <dri-devel@lists.freedesktop.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>
Subject: Re: linux-next: build warnings after merge of the drm tree
Date: Mon, 16 Nov 2020 10:44:44 +1100	[thread overview]
Message-ID: <20201116104444.044486ea@canb.auug.org.au> (raw)
In-Reply-To: <20201105175031.00e0b081@canb.auug.org.au>


[-- Attachment #1.1: Type: text/plain, Size: 762 bytes --]

Hi all,

On Thu, 5 Nov 2020 17:50:31 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
> 
> After merging the drm tree, today's linux-next build (htmldocs) produced
> these warnings:
> 
> include/linux/dma-buf-map.h:106: warning: Excess function parameter 'vaddr' description in 'DMA_BUF_MAP_INIT_VADDR'
> include/linux/dma-buf-map.h:106: warning: Function parameter or member 'vaddr_' not described in 'DMA_BUF_MAP_INIT_VADDR'
> include/linux/dma-buf-map.h:106: warning: Excess function parameter 'vaddr' description in 'DMA_BUF_MAP_INIT_VADDR'
> 
> Introduced by commit
> 
>   20e76f1a7059 ("dma-buf: Use struct dma_buf_map in dma_buf_vunmap() interfaces")

I am still getting these warnings.

-- 
Cheers,
Stephen Rothwell

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

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2020-11-15 23:45 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-05  6:50 linux-next: build warnings after merge of the drm tree Stephen Rothwell
2020-11-05  6:50 ` Stephen Rothwell
2020-11-15 23:44 ` Stephen Rothwell [this message]
2020-11-15 23:44   ` Stephen Rothwell
2020-12-14 19:50   ` Stephen Rothwell
2020-12-14 19:50     ` Stephen Rothwell
2020-12-15  2:47     ` Stephen Rothwell
2020-12-15  2:47       ` Stephen Rothwell
2020-12-15  9:42       ` Daniel Vetter
2020-12-15  9:42         ` Daniel Vetter
  -- strict thread matches above, loose matches on Subject: below --
2025-11-06  4:11 Stephen Rothwell
2025-12-16  1:04 ` Stephen Rothwell
2025-11-06  4:05 Stephen Rothwell
2025-11-06  4:03 Stephen Rothwell
2025-01-13  5:03 Stephen Rothwell
2024-02-19  5:21 Stephen Rothwell
2023-06-13  6:29 Stephen Rothwell
2023-06-13  6:29 ` Stephen Rothwell
2023-01-05  3:47 Stephen Rothwell
2023-01-05  3:47 ` Stephen Rothwell
2021-06-03  9:32 Stephen Rothwell
2021-06-03  9:32 ` Stephen Rothwell
2021-07-08  2:20 ` Stephen Rothwell
2021-07-08  2:20   ` Stephen Rothwell
2021-08-10  9:26   ` Stephen Rothwell
2021-08-10 10:14     ` Daniel Vetter
2021-08-10 10:38       ` Stephen Rothwell
2021-08-10 10:50         ` Daniel Vetter
2021-08-10 11:01           ` Stephen Rothwell
2021-08-10 12:39             ` Daniel Vetter
2021-08-10 13:21               ` Stephen Rothwell
2021-04-01  7:32 Stephen Rothwell
2021-04-01  7:32 ` Stephen Rothwell
2021-04-21  6:30 ` Stephen Rothwell
2021-04-21  6:30   ` Stephen Rothwell
2017-11-01  3:16 Stephen Rothwell
2017-11-01  9:58 ` Boris Brezillon
2017-05-19  2:07 Stephen Rothwell
2017-05-19 17:49 ` Eric Anholt
2017-05-25  1:49   ` Stephen Rothwell
2017-06-02  3:59     ` Stephen Rothwell
2017-06-02 21:05       ` Eric Anholt
2017-06-02 23:40         ` Stephen Rothwell
2017-06-03  0:45           ` Eric Anholt
2017-06-03  1:26             ` Stephen Rothwell
2017-02-23 23:27 Stephen Rothwell
2017-02-19 23:48 Stephen Rothwell
2012-10-04  2:21 Stephen Rothwell
2012-09-04  3:58 Stephen Rothwell
2012-09-04  5:31 ` Guenter Roeck
2012-09-04  6:40 ` Sedat Dilek
2012-09-04  8:22   ` Dave Airlie
2012-09-04  8:58     ` Sedat Dilek

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=20201116104444.044486ea@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=tzimmermann@suse.de \
    /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.