From: Markus Elfring <Markus.Elfring@web.de>
To: Biancaa Ramesh <biancaa2210329@ssn.edu.in>,
linux-media@vger.kernel.org, Andy Walls <awalls@md.metrocast.net>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: cx18: kernel memory safety check in a block
Date: Tue, 21 Oct 2025 20:33:50 +0200 [thread overview]
Message-ID: <2638dc88-a6e7-4b3c-8783-629bcfcd7d4b@web.de> (raw)
In-Reply-To: <20251021175711.49252-1-biancaa2210329@ssn.edu.in>
…
> ---
> drivers/media/pci/cx18/cx18-queue.c | 11 +++++++++--
…
Thanks for your try to improve the implementation of the function “cx18_stream_alloc”.
https://elixir.bootlin.com/linux/v6.18-rc2/source/drivers/media/pci/cx18/cx18-queue.c#L332-L408
I miss some information so far.
1. Helpful change description
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.18-rc2#n45
2. Subsystem specification
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.18-rc2#n646
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/drivers/media/pci/cx18/cx18-queue.c
3. More appropriate recipient selection
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.18-rc2#n231
…
> --
> ::DISCLAIMER::
…
> The
> contents of this e-mail and any attachment(s) are confidential and
…
Such hints are probably misplaced for communication by the means of public mailing lists.
See also once more:
https://subspace.kernel.org/etiquette.html#do-not-include-confidentiality-disclaimers
Regards,
Markus
prev parent reply other threads:[~2025-10-21 18:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 17:57 [PATCH] " Biancaa Ramesh
2025-10-21 18:33 ` 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=2638dc88-a6e7-4b3c-8783-629bcfcd7d4b@web.de \
--to=markus.elfring@web.de \
--cc=awalls@md.metrocast.net \
--cc=biancaa2210329@ssn.edu.in \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.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®