From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Aline Santana Cordeiro <alinesantanacordeiro@gmail.com>,
Deepak R Varma <mh12gx2825@gmail.com>,
Martiros Shakhzadyan <vrzh@vrzh.net>
Subject: Re: [GIT PULL FOR v5.14] More Outreachy cleanups (v2)
Date: Mon, 17 May 2021 15:57:18 +0200 [thread overview]
Message-ID: <20210517155718.196a6089@coco.lan> (raw)
In-Reply-To: <706ba93e-fa1c-34ce-8c54-d8a1c442811e@xs4all.nl>
Em Fri, 30 Apr 2021 12:11:22 +0200
Hans Verkuil <hverkuil@xs4all.nl> escreveu:
> This supersedes an earlier PR. This v2 adds more patches from Martiros and
> Deepak.
>
> Regards,
>
> Hans
>
> The following changes since commit 6756ae29420f849de4dc5c41f9fe948450b09285:
>
> media: staging: media: atomisp: pci: Format comments according to coding-style in file atomisp_cmd.h (2021-04-21 14:07:01 +0200)
>
> are available in the Git repository at:
>
> git://linuxtv.org/hverkuil/media_tree.git tags/br-v5.14-out1
>
> for you to fetch changes up to 68dc2d762b637dd980f8dcc9e762da8cb788b57e:
>
> staging: media: atomisp: remove unwanted dev_*() calls (2021-04-30 11:49:40 +0200)
>
> ----------------------------------------------------------------
> Tag branch
>
> ----------------------------------------------------------------
> Aline Santana Cordeiro (5):
> staging: media: atomisp: pci: Balance braces around conditional statements in file atomisp_cmd.c
> staging: media: atomisp: pci: Balance braces around conditional statements in file atomisp_compat_css20.c
> staging: media: atomisp: pci: Balance braces around conditional statements in file atomisp_subdev.c
> staging: media: atomisp: pci: Balance braces around conditional statements in file atomisp_v4l2.c
> staging: media: tegra-video: Align line break to match with the open parenthesis in file vi.c
>
> Deepak R Varma (8):
> staging: media: atomisp: balance braces around if...else block
> staging: media: atomisp: remove unnecessary braces
> staging: media: atomisp: use __func__ over function names
> staging: media: atomisp: reformat code comment blocks
> staging: media: atomisp: fix CamelCase variable naming
> staging: media: atomisp: replace raw pr_*() by dev_dbg()
> staging: media: atomisp: remove unnecessary pr_info calls
> staging: media: atomisp: remove unwanted dev_*() calls
>
> Martiros Shakhzadyan (9):
> staging: media: atomisp: Fix sh_css.c brace coding style issues
> staging: media: atomisp: Remove redundant assertions in sh_css.c
> staging: media: atomisp: Fix the rest of sh_css.c brace issues
> staging: media: atomisp: Remove all redundant assertions in sh_css.c
> staging: media: atomisp: Remove a superfluous else clause in sh_css.c
> staging: media: atomisp: Replace if else clause with a ternary
> staging: media: atomisp: Fix alignment and line length issues
> staging: media: atomisp: Refactor ia_css_stream_load()
> staging: media: atomisp: Fix line split style issues
I ended not applying two patches from this series:
- staging: media: atomisp: use __func__ over function names
Dan requested some changes on it, as it has several dev_dbg() calls
used just for tracing. I sent a reply with a few additional issues;
- staging: media: atomisp: remove unwanted dev_*() calls
This one didn't apply. Is it touching the same lines the first patch
changed? If so, please merge both into a single one, after applying
the fixes I mentioned on my e-mail:
https://lore.kernel.org/linux-media/20210517154448.7bb8be17@coco.lan/T/#ma9ded10c22aaa86de74babf1bd2a2320c3dac70b
The remaining ones were applied.
Thanks!
Mauro
prev parent reply other threads:[~2021-05-17 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 10:11 [GIT PULL FOR v5.14] More Outreachy cleanups (v2) Hans Verkuil
2021-04-30 10:30 ` [GIT PULL FOR v5.14] More Outreachy cleanups (v2) (#73995) Jenkins
2021-05-17 13:57 ` Mauro Carvalho Chehab [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=20210517155718.196a6089@coco.lan \
--to=mchehab+huawei@kernel.org \
--cc=alinesantanacordeiro@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mh12gx2825@gmail.com \
--cc=vrzh@vrzh.net \
/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