From: Markus Elfring <Markus.Elfring@web.de>
To: Biancaa Ramesh <biancaa2210329@ssn.edu.in>,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
Sumit Semwal <sumit.semwal@linaro.org>
Cc: linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org,
lkp@intel.com, "Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH v2] Signed-off-by: Biancaa Ramesh …
Date: Wed, 22 Oct 2025 13:14:24 +0200 [thread overview]
Message-ID: <d1461717-1a58-46f7-b8fd-a185aaf90828@web.de> (raw)
In-Reply-To: <20251022043108.7197-1-biancaa2210329@ssn.edu.in>
> dma-buf: improve dma_buf_show_fdinfo output
…
> This patch also fixes incorrect …
See also:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.18-rc2#n94
> Closes: https://lore.kernel.org/oe-kbuild-all/202510220802.svbgdYsJ-lkp@intel.com/
Not yet.
Please use a more appropriate patch subject for the proposed adjustment
of the function “dma_buf_show_fdinfo”.
https://elixir.bootlin.com/linux/v6.18-rc2/source/drivers/dma-buf/dma-buf.c#L570-L582
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.18-rc2#n396
> ---
> drivers/dma-buf/dma-buf.c | 26 ++++++++++++--------------
…
Some contributors would appreciate patch version descriptions.
https://lore.kernel.org/all/?q=%22This+looks+like+a+new+version+of+a+previously+submitted+patch%22
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.18-rc2#n310
…
> +++ b/drivers/dma-buf/dma-buf.c
> @@ -571,24 +571,22 @@ static long dma_buf_ioctl(struct file *file,
> }
> }
>
> -static void dma_buf_show_fdinfo(struct seq_file *s, struct file *f)
> +static void dma_buf_show_fdinfo(struct seq_file *s, struct file *file)
> {
…
…
> - seq_printf(s, "flags:\t%lu\n", f->f_flags);
> - seq_printf(s, "size:\t%llu\n", dmabuf->size);
* Why does such a diff representation contain space characters instead of tab characters?
* Did you refer to a source code variant before the commit bcc071110aeacd28a87525a2442dd96eab145a3c
("dma-buf: add show_fdinfo handler") from 2019-06-14?
…
> --
> ::DISCLAIMER::
…
> The
> contents of this e-mail and any attachment(s) are confidential and
…
Please avoid such unwanted information for communication by the means of public mailing lists.
https://subspace.kernel.org/etiquette.html#do-not-include-confidentiality-disclaimers
Regards,
Markus
prev parent reply other threads:[~2025-10-22 11:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 4:31 [PATCH v2] Signed-off-by: Biancaa Ramesh <biancaa2210329@ssn.edu.in> Biancaa Ramesh
2025-10-22 10:07 ` Jani Nikula
2025-10-22 11:14 ` Markus Elfring [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=d1461717-1a58-46f7-b8fd-a185aaf90828@web.de \
--to=markus.elfring@web.de \
--cc=biancaa2210329@ssn.edu.in \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lkp@intel.com \
--cc=sumit.semwal@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®