doc: add dma-buf IOCTL code to table

The code 'b' is used for dma-buf IOCTLs.

Signed-off-by: Simon Ser <contact@emersion.fr>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Daniel Vetter <daniel@ffwll.ch>
Cc: Christian König <christian.koenig@amd.com>
Cc: Sumit Semwal <sumit.semwal@linaro.org>
---
 Documentation/userspace-api/ioctl/ioctl-number.rst | 1 +
 1 file changed, 1 insertion(+)

Am 28.11.22 um 14:39 schrieb Simon Ser:
> The code 'b' is used for dma-buf IOCTLs.
>
> Signed-off-by: Simon Ser <contact@emersion.fr>
> Cc: Linus Torvalds <torvalds@linux-foundation.org>
> Cc: Daniel Vetter <daniel@ffwll.ch>
> Cc: Christian König <christian.koenig@amd.com>
> Cc: Sumit Semwal <sumit.semwal@linaro.org>

Reviewed-by: Christian König <christian.koenig@amd.com>

Should I also push this?

> ---
>   Documentation/userspace-api/ioctl/ioctl-number.rst | 1 +
>   1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/userspace-api/ioctl/ioctl-number.rst b/Documentation/userspace-api/ioctl/ioctl-number.rst
> index 5f81e2a24a5c..184a7a222701 100644
> --- a/Documentation/userspace-api/ioctl/ioctl-number.rst
> +++ b/Documentation/userspace-api/ioctl/ioctl-number.rst
> @@ -221,6 +221,7 @@ Code  Seq#    Include File                                           Comments
>   'a'   00-0F  drivers/crypto/qat/qat_common/adf_cfg_common.h          conflict! qat driver
>   'b'   00-FF                                                          conflict! bit3 vme host bridge
>                                                                        <mailto:natalia@nikhefk.nikhef.nl>
> +'b'   00-0F  linux/dma-buf.h                                         conflict!
>   'c'   all    linux/cm4000_cs.h                                       conflict!
>   'c'   00-7F  linux/comstats.h                                        conflict!
>   'c'   00-7F  linux/coda.h                                            conflict!

On Tuesday, November 29th, 2022 at 10:56, Christian König <christian.koenig@amd.com> wrote:

> Should I also push this?

I can push to drm-misc-next, but is that the suitable repo?

On Tuesday, January 10th, 2023 at 12:53, Christian König <christian.koenig@amd.com> wrote:

> Am 10.01.23 um 12:49 schrieb Simon Ser:
> 
> > On Tuesday, November 29th, 2022 at 10:56, Christian König christian.koenig@amd.com wrote:
> > 
> > > Should I also push this?
> > > I can push to drm-misc-next, but is that the suitable repo?
> 
> I think so, unless you think that this is a necessary bug fix which
> should be backported.

Thanks! I pushed it there.