From: Martiros Shakhzadyan <vrzh@vrzh.net>
To: Hans Verkuil <hverkuil@xs4all.nl>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-media@vger.kernel.org, Martiros Shakhzadyan <vrzh@vrzh.net>
Subject: Re: [PATCH] staging: media: atomisp: cleaning up sh_css.c
Date: Thu, 15 Apr 2021 12:29:18 -0400 [thread overview]
Message-ID: <YHhp3vfF2KH9nKT0@coplandos.local> (raw)
In-Reply-To: <e7d21188-3f7e-1b8f-59b0-144713bd918d@xs4all.nl>
On Thu, Apr 15, 2021 at 03:59:25PM +0200, Hans Verkuil wrote:
> Hi Martiros,
>
> If you look at other patch series, you'll see that they follow this pattern:
>
> [PATCH x/y]
>
> and for the cover letter: [PATCH 0/y]
>
> It's recommended to follow that rule.
>
> On 15/04/2021 02:50, Martiros Shakhzadyan wrote:
> > The following set of patches for sh_css.c aims to resolve coding style issues
> > and remove redundancies.
> >
> > Martiros Shakhzadyan (9):
> > staging: media: atomisp: [1/6] Fix sh_css.c brace coding style issues
> > staging: media: atomisp: [2/6] Fix sh_css.c brace coding style issues
> > staging: media: atomisp: [3/6] Fix sh_css.c brace coding style issues
> > staging: media: atomisp: [4/6] Fix sh_css.c brace coding style issues
> > staging: media: atomisp: [5/6] Fix sh_css.c brace coding style issues
> > staging: media: atomisp: [6/6] Fix sh_css.c brace coding style issues\
>
> Why split this up in 6 patches? Just combine it in one. It's all the same thing
> for the same source.
>
> > staging: media: atomisp: Use goto instead of return in ia_css_init()
> > staging: media: atomisp: [1/2] Remove redundant assertions in sh_css.c
> > staging: media: atomisp: [2/2] Remove redundant assertions in sh_css.c
>
> Ditto for these two.
>
> Regards,
>
> Hans
>
Gotcha - will resubmit all following this rule (save for the rejected
patch) - Thanks!
> >
> > drivers/staging/media/atomisp/pci/sh_css.c | 266 ++++++++-------------
> > 1 file changed, 105 insertions(+), 161 deletions(-)
> >
>
prev parent reply other threads:[~2021-04-15 16:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 0:50 [PATCH] staging: media: atomisp: cleaning up sh_css.c Martiros Shakhzadyan
2021-04-15 0:50 ` [PATCH] staging: media: atomisp: [1/6] Fix sh_css.c brace coding style issues Martiros Shakhzadyan
2021-04-15 0:50 ` [PATCH] staging: media: atomisp: [2/6] " Martiros Shakhzadyan
2021-04-15 0:51 ` [PATCH] staging: media: atomisp: [3/6] " Martiros Shakhzadyan
2021-04-15 0:51 ` [PATCH] staging: media: atomisp: [4/6] " Martiros Shakhzadyan
2021-04-15 0:51 ` [PATCH] staging: media: atomisp: [5/6] " Martiros Shakhzadyan
2021-04-15 0:51 ` [PATCH] staging: media: atomisp: [6/6] " Martiros Shakhzadyan
2021-04-15 0:51 ` [PATCH] staging: media: atomisp: Use goto instead of return in ia_css_init() Martiros Shakhzadyan
2021-04-15 13:56 ` Hans Verkuil
2021-04-15 16:39 ` Martiros Shakhzadyan
2021-04-15 0:51 ` [PATCH] staging: media: atomisp: [1/2] Remove redundant assertions in sh_css.c Martiros Shakhzadyan
2021-04-15 13:46 ` Hans Verkuil
2021-04-15 0:51 ` [PATCH] staging: media: atomisp: [2/2] " Martiros Shakhzadyan
2021-04-15 13:59 ` [PATCH] staging: media: atomisp: cleaning up sh_css.c Hans Verkuil
2021-04-15 16:29 ` Martiros Shakhzadyan [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=YHhp3vfF2KH9nKT0@coplandos.local \
--to=vrzh@vrzh.net \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
/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