From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Marc Gonzalez <marc.w.gonzalez@free.fr>
Cc: linux-media@vger.kernel.org
Subject: Re: [RFC] Documentation clarifications
Date: Tue, 4 Jun 2019 14:26:58 -0300 [thread overview]
Message-ID: <20190604142658.0ea99881@coco.lan> (raw)
In-Reply-To: <e9d01085-168f-2cd8-9aef-e8b632489b8e@free.fr>
Em Tue, 4 Jun 2019 18:41:44 +0200
Marc Gonzalez <marc.w.gonzalez@free.fr> escreveu:
> Not sure about these changes, hence the RFC (some are quite trivial)
Looks ok to me. You should submit it as a patch, though, with your SOB.
See https://linuxtv.org/wiki/index.php/Development:_How_to_submit_patches.
>
> diff --git a/Documentation/media/kapi/dtv-core.rst b/Documentation/media/kapi/dtv-core.rst
> index ac005b46f23e..9a74b8ba64b7 100644
> --- a/Documentation/media/kapi/dtv-core.rst
> +++ b/Documentation/media/kapi/dtv-core.rst
> @@ -11,8 +11,8 @@ Digital TV devices are implemented by several different drivers:
>
> - Frontend drivers that are usually implemented as two separate drivers:
>
> - - A tuner driver that implements the logic with commands the part of the
> - hardware with is responsible to tune into a digital TV transponder or
> + - A tuner driver that implements the logic which commands the part of
> + the hardware responsible for tuning into a digital TV transponder or
> physical channel. The output of a tuner is usually a baseband or
> Intermediate Frequency (IF) signal;
>
> diff --git a/include/media/dvbdev.h b/include/media/dvbdev.h
> index 881ca461b7bb..8e47411cf1d9 100644
> --- a/include/media/dvbdev.h
> +++ b/include/media/dvbdev.h
> @@ -86,8 +86,8 @@ struct dvb_frontend;
> * @priv: private data
> * @device: pointer to struct device
> * @module: pointer to struct module
> - * @mfe_shared: mfe shared: indicates mutually exclusive frontends
> - * Thie usage of this flag is currently deprecated
> + * @mfe_shared: indicates mutually exclusive frontends.
> + * Use of this flag is currently deprecated.
> * @mfe_dvbdev: Frontend device in use, in the case of MFE
> * @mfe_lock: Lock to prevent using the other frontends when MFE is
> * used.
Thanks,
Mauro
next prev parent reply other threads:[~2019-06-04 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 16:41 [RFC] Documentation clarifications Marc Gonzalez
2019-06-04 17:26 ` Mauro Carvalho Chehab [this message]
2019-06-05 8:08 ` Marc Gonzalez
2019-06-05 8:32 ` Mauro Carvalho Chehab
2019-06-05 11:59 ` [PATCH] media: docs: fix minor typos Marc Gonzalez
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=20190604142658.0ea99881@coco.lan \
--to=mchehab@kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=marc.w.gonzalez@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.