From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Bohdan Derkach <bohdandmarcus@gmail.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
hansg@kernel.org, mchehab@kernel.org, gregkh@linuxfoundation.org,
andy@kernel.org, sakari.ailus@linux.intel.com,
linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] media: atomisp: fix block comment formatting style
Date: Wed, 1 Jul 2026 12:30:50 +0300 [thread overview]
Message-ID: <akTeSuxmA8PesfAt@ashevche-desk.local> (raw)
In-Reply-To: <CANqab0096R4gKrwfKF78iyQt2aM0qQJoSwrBKBqMiZxna60rsg@mail.gmail.com>
On Wed, Jul 01, 2026 at 11:51:43AM +0300, Bohdan Derkach wrote:
First of all, do not top-post!
Second, do not send HTML, the only plain text is what is considered.
> On Wed, Jul 1, 2026 at 11:42 AM Bohdan Derkach <bohdandmarcus@gmail.com> wrote:
> > You are completely right about the indentation and line wraps. Dan
> > Carpenter also pointed this out to me yesterday, and I have already
> > prepared a v4 that fixes all of these issues perfectly. I am strictly
> > following the rule to wait a full 24 hours between sending versions, so I
> > will send v4 later today.
> >
> > Regarding your question about whether this is the only issue in the driver:
> > I understand that sending a patch for a single block comment in a 100k LoC
> > driver is a very small contribution. Since this is my very first patch to
> > the Linux kernel, my main goal was to learn the correct workflow (git
> > send-email, formatting versions, acting on feedback) before sending larger
> > patch series.
> >
> > Once this v4 is accepted and I am confident that my setup is correct, my
> > next step is to grep through the rest of atomisp to fix similar block
> > comments and submit them as a proper patch series.
It really doesn't matter if this is a single place fix or not, the part of
the process is to try to fix the whole class of the problems at once.
Also check that your code is based on latest and greatest maintainer's tip.
(It's located somewhere on git.linuxtv.org with atomisp in the tree name.)
> > Thank you for your patience and for guiding a newcomer!
You're welcome.
> > On Wed, Jul 1, 2026 at 11:31 AM Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> >>
> >> On Tue, Jun 30, 2026 at 7:06 PM Bohdan D. Marcus
> >> <bohdandmarcus@gmail.com> wrote:
> >> >
> >> > Fix a block comment formatting warning reported by
> >> > checkpatch.pl in atomisp_cmd.c to conform to the
> >> > Linux kernel coding style.
> >>
> >> Almost the same comments as per v2. Please, slow down, read other
> >> comments and act accordingly.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-07-01 9:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 16:04 [PATCH v3] media: atomisp: fix block comment formatting style Bohdan D. Marcus
2026-07-01 8:30 ` Andy Shevchenko
[not found] ` <CANqab03_SQFDb38wkXBMUiJ1Xk-g9_ZpqvOUo+nQyR+SsVnsFQ@mail.gmail.com>
2026-07-01 8:51 ` Bohdan Derkach
2026-07-01 9:30 ` Andy Shevchenko [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=akTeSuxmA8PesfAt@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=bohdandmarcus@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--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