linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Martin Weidenauer <martin@weidenauer.cc>
Cc: Woohee Yang <woohee9527@gmail.com>,
	Jongmin Kim <jmkim@debian.org>,
	hansg@kernel.org,  mchehab@kernel.org,
	sakari.ailus@linux.intel.com, andy@kernel.org,
	 gregkh@linuxfoundation.org, linux-media@vger.kernel.org,
	 linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
	 ~lkcamp/patches@lists.sr.ht, koike@igalia.com
Subject: Re: [PATCH] staging: atomisp: isp: fix open brace on new line
Date: Tue, 15 Jul 2025 00:38:47 +0300	[thread overview]
Message-ID: <CAHp75VcvOaSPbrpurRAjrvwW992qiP-ffZcroQ-feg=_PAoquQ@mail.gmail.com> (raw)
In-Reply-To: <4289C286-62A1-4C22-9A03-E6CD3731F3D7@weidenauer.cc>

On Mon, Jul 14, 2025 at 10:39 PM Martin Weidenauer <martin@weidenauer.cc> wrote:
> On 14 July 2025 19:47:41 CEST, Andy Shevchenko <andy.shevchenko@gmail.com> wrote:

> >Guys, please, coordinate and issue only one (or a few) patch(es) per
> >an issue. No need to send zillions patches for the same problem
> >file-by-file.

> >On Mon, Jul 14, 2025 at 6:34 PM Martin Weidenauer <martin@weidenauer.cc> wrote:
> >>
> >> Fix checkpatch error "ERROR: that open brace { should be on the previous line"
> >> in ia_css_dvs.host.c:277.

> I deeply apologize, however this was the instruction of our workshop in DebConf by Helen Koike <koike@igalia.com>

This may be okay for the driver that consists of let's say less than
10 files, AtomISP consists of dozens of files in several (nested)
folders. It's not a good example for such an approach.

> Here is the link to the exact workshop:
> <https://debconf25.debconf.org/talks/55-submit-your-first-contribution-to-the-linux-kernel/>

Hmm... this really needs an update to explain how to work with the
drivers that contain many files and literally tens of thousands lines
of code.

In any case the problem with your contribution is not the code, the
absence of coordination and possibility to clash with somebody else.
Also it looks like a DDoS attack against maintainers capacity. The
smaller patches are and the more of them --- the less the usefulness
of all this activity as at some point that floods the maintainer's
mailbox.

TL:DR; (always) Use common sense!


-- 
With Best Regards,
Andy Shevchenko

  reply	other threads:[~2025-07-14 21:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-14 15:34 [PATCH] staging: atomisp: isp: fix open brace on new line Martin Weidenauer
2025-07-14 17:47 ` Andy Shevchenko
2025-07-14 19:38   ` Martin Weidenauer
2025-07-14 21:38     ` Andy Shevchenko [this message]
2025-07-14 21:54       ` Martin Weidenauer
2025-07-15  6:57         ` Andy Shevchenko
2025-07-15  7:04           ` Greg KH
2025-07-15  7:26             ` Andy Shevchenko
2025-07-15  7:53 ` Andy Shevchenko
  -- strict thread matches above, loose matches on Subject: below --
2025-07-14 13:19 Martin Weidenauer
2025-07-14 13:24 ` Greg KH
2025-07-14 13:51   ` Martin Weidenauer
2025-07-14 15:27     ` Andy Shevchenko

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='CAHp75VcvOaSPbrpurRAjrvwW992qiP-ffZcroQ-feg=_PAoquQ@mail.gmail.com' \
    --to=andy.shevchenko@gmail.com \
    --cc=andy@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hansg@kernel.org \
    --cc=jmkim@debian.org \
    --cc=koike@igalia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=martin@weidenauer.cc \
    --cc=mchehab@kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=woohee9527@gmail.com \
    --cc=~lkcamp/patches@lists.sr.ht \
    /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;
as well as URLs for NNTP newsgroup(s).