From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
linuxarm@huawei.com, mauro.chehab@huawei.com,
Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] media: add a subsystem profile documentation
Date: Mon, 1 Mar 2021 10:40:01 +0100 [thread overview]
Message-ID: <20210301104001.4689ee2f@coco.lan> (raw)
In-Reply-To: <CAKXUXMwviRBB_xnuBLRFRhg6eBXKjMakQLaAfqQiQEsACJjfRw@mail.gmail.com>
Em Sat, 27 Feb 2021 12:13:28 +0100
Lukas Bulwahn <lukas.bulwahn@gmail.com> escreveu:
> On Thu, Feb 25, 2021 at 2:41 PM Mauro Carvalho Chehab
> <mchehab+huawei@kernel.org> wrote:
> >
> > Document the basic policies of the media subsystem profile.
> >
> > Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> > ---
> >
> > +
> > +Media development uses checkpatch on strict mode to verify the code style,
> > +e. g.::
> > +
> > + $ ./script/checkpatch.pl --strict
>
> Just a typo: script -> scripts
>
Fixed in v3, thanks for reviewing it!
Thanks,
Mauro
next prev parent reply other threads:[~2021-03-01 9:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 13:41 [PATCH v2] media: add a subsystem profile documentation Mauro Carvalho Chehab
2021-02-27 0:23 ` Randy Dunlap
2021-03-01 9:39 ` Mauro Carvalho Chehab
2021-02-27 11:13 ` Lukas Bulwahn
2021-03-01 9:40 ` Mauro Carvalho Chehab [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-18 12:36 [Ksummit-discuss] [PATCH] " Laurent Pinchart
2019-09-18 13:59 ` [PATCH v2] " Mauro Carvalho Chehab
2019-09-18 14:07 ` André Almeida
2019-09-18 14:11 ` 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=20210301104001.4689ee2f@coco.lan \
--to=mchehab+huawei@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lukas.bulwahn@gmail.com \
--cc=mauro.chehab@huawei.com \
--cc=mchehab@kernel.org \
--cc=rdunlap@infradead.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 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.