From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Hans Verkuil <hverkuil+cisco@kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Jonathan Corbet <corbet@lwn.net>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Nicolas Dufresne <nicolas.dufresne@collabora.com>,
Ricardo Ribalda <ribalda@chromium.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Sean Young <sean@mess.org>
Subject: Re: [PATCH 2/2] docs: media: media-committer: do some editorial changes
Date: Wed, 4 Feb 2026 16:07:04 +0100 [thread overview]
Message-ID: <20260204160704.0741bbba@localhost> (raw)
In-Reply-To: <ada3056177e5e4e65119fb1b617777a680534e64.1770215865.git.mchehab+huawei@kernel.org>
On Wed, 4 Feb 2026 15:37:45 +0100
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:
> Do some editorial changes to make it look clearer:
...
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> ---
> .../driver-api/media/media-committer.rst | 97 ++++++++++---------
> 1 file changed, 51 insertions(+), 46 deletions(-)
...
> @@ -85,7 +89,7 @@ rules::
>
> I agree to follow the Kernel development rules described at:
>
> - https://www.kernel.org/doc/html/latest/driver-api/media/media-committer.rst
> + https://www.kernel.org/doc/html/latest/driver-api/media/media-committers.rst
>
> and to the Linux Kernel development process rules.
Heh, this change is obviously wrong, except if we rename the rst document
to also be media-committers.rst, which sounds a good idea to me:
- Use "media-committers" for both the .rst file and for the git tree.
So, please rename the file on v8 (or otherwise fix it here)
--
Thanks,
Mauro
next prev parent reply other threads:[~2026-02-04 15:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 10:53 [PATCHv7 0/3] docs: media: multicommitters model documentation Hans Verkuil
2026-01-27 10:53 ` [PATCHv7 1/3] docs: media: update maintainer-entry-profile for multi-committers Hans Verkuil
2026-02-05 11:37 ` Bryan O'Donoghue
2026-02-05 18:03 ` kernel test robot
2026-01-27 10:53 ` [PATCHv7 2/3] docs: media: document Media Maintainers Hans Verkuil
2026-02-05 11:38 ` Bryan O'Donoghue
2026-02-05 14:24 ` Nicolas Dufresne
2026-02-05 16:59 ` Laurent Pinchart
2026-02-06 8:30 ` Jacopo Mondi
2026-01-27 10:53 ` [PATCHv7 3/3] docs: media: document media multi-committers rules and process Hans Verkuil
2026-02-04 14:36 ` [PATCHv7 0/3] docs: media: multicommitters model documentation Mauro Carvalho Chehab
2026-02-04 14:37 ` [PATCH 1/2] docs: media: maintainer-entry-profile: do some editorial reviews Mauro Carvalho Chehab
2026-02-04 14:37 ` [PATCH 2/2] docs: media: media-committer: do some editorial changes Mauro Carvalho Chehab
2026-02-04 15:07 ` Mauro Carvalho Chehab [this message]
2026-02-05 11:52 ` Hans Verkuil
2026-02-05 13:51 ` Mauro Carvalho Chehab
2026-02-05 13:58 ` Hans Verkuil
2026-02-05 11:25 ` [PATCH 1/2] docs: media: maintainer-entry-profile: do some editorial reviews Hans Verkuil
2026-02-05 13:53 ` Mauro Carvalho Chehab
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=20260204160704.0741bbba@localhost \
--to=mchehab+huawei@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=corbet@lwn.net \
--cc=hverkuil+cisco@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nicolas.dufresne@collabora.com \
--cc=ribalda@chromium.org \
--cc=sakari.ailus@linux.intel.com \
--cc=sean@mess.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