From: "Hanne-Lotta Mäenpää" <hannelotta@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
mchehab@kernel.org, ribalda@chromium.org, hverkuil@xs4all.nl,
hljunggr@cisco.com, dave.jiang@intel.com, jgg@ziepe.ca,
saeedm@nvidia.com, Jonathan.Cameron@huawei.com, corbet@lwn.net,
ilpo.jarvinen@linux.intel.com, mario.limonciello@amd.com,
W_Armin@gmx.de, mpearson-lenovo@squebb.ca,
skhan@linuxfoundation.org
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev
Subject: Re: [PATCH v2 1/4] docs: Improve grammar in Userspace API/DVB API
Date: Wed, 11 Jun 2025 14:33:12 +0300 [thread overview]
Message-ID: <5dad612b-495b-4f1c-82ff-e8ed4ef34c07@gmail.com> (raw)
In-Reply-To: <aDAOhl7gKhkcTEjk@archie.me>
On 5/23/25 08:58, Bagas Sanjaya wrote:
> On Thu, May 22, 2025 at 02:52:52PM +0300, Hanne-Lotta Mäenpää wrote:
>> #. On Satellite and Cable delivery systems, the bandwidth depends on
>> - the symbol rate. So, the Kernel will silently ignore any setting
>> - :ref:`DTV-BANDWIDTH-HZ`. I will however fill it back with a
>> - bandwidth estimation.
>> + the symbol rate. The kernel will silently ignore any setting
>> + :ref:`DTV-BANDWIDTH-HZ` and overwrites it with bandwidth estimation.
> "The kernel will silently ignore any :ref:`DTV-BANDWIDTH-HZ` setting ..."
>>
>> Such bandwidth estimation takes into account the symbol rate set with
>> :ref:`DTV-SYMBOL-RATE`, and the rolloff factor, with is fixed for
>
> Thanks.
>
Hello,
What is the best way to send an update on this patch, now that patches
3/4 and 4/4 have been applied, but 1/4 and 2/4 have not been applied?
Do I send v3 for the first two only?
Any guidance is greatly appreciated, since I am new to kernel development.
Best regards,
Hanne-Lotta Mäenpää
next prev parent reply other threads:[~2025-06-11 11:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 11:52 [PATCH v2 1/4] docs: Improve grammar in Userspace API/DVB API Hanne-Lotta Mäenpää
2025-05-22 11:52 ` [PATCH v2 2/4] docs: Improve grammar, formatting in Video4Linux Hanne-Lotta Mäenpää
2025-05-23 6:03 ` Bagas Sanjaya
2025-05-22 11:52 ` [PATCH v2 3/4] docs: Improve grammar in Userspace API/fwctl Hanne-Lotta Mäenpää
2025-05-22 14:59 ` Dave Jiang
2025-05-23 6:09 ` Bagas Sanjaya
2025-06-09 21:12 ` Jonathan Corbet
2025-06-10 8:24 ` Hanne-Lotta Mäenpää
2025-05-22 11:52 ` [PATCH v2 4/4] docs: Fix typos, improve grammar in Userspace API Hanne-Lotta Mäenpää
2025-05-22 12:00 ` Mark Pearson
2025-05-23 6:14 ` Bagas Sanjaya
2025-06-09 21:13 ` Jonathan Corbet
2025-06-10 8:25 ` Hanne-Lotta Mäenpää
2025-05-23 5:58 ` [PATCH v2 1/4] docs: Improve grammar in Userspace API/DVB API Bagas Sanjaya
2025-06-11 11:33 ` Hanne-Lotta Mäenpää [this message]
2025-06-11 12:50 ` Jonathan Corbet
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=5dad612b-495b-4f1c-82ff-e8ed4ef34c07@gmail.com \
--to=hannelotta@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=W_Armin@gmx.de \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=dave.jiang@intel.com \
--cc=hljunggr@cisco.com \
--cc=hverkuil@xs4all.nl \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mchehab@kernel.org \
--cc=mpearson-lenovo@squebb.ca \
--cc=ribalda@chromium.org \
--cc=saeedm@nvidia.com \
--cc=skhan@linuxfoundation.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