From: Sakari Ailus <sakari.ailus@iki.fi>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Ayush Kumar <ayushkr0s@gmail.com>,
hansg@kernel.org, mchehab@kernel.org,
sakari.ailus@linux.intel.com, andy@kernel.org,
gregkh@linuxfoundation.org, hverkuil@kernel.org,
ribalda@chromium.org, abdelrahmanfekry375@gmail.com,
santiagorr@riseup.net, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
kernel-newbies@vger.kernel.org
Subject: Re: [PATCH] media: atomisp: coding style: Move trailing statements to next line
Date: Sun, 19 Apr 2026 15:45:52 +0300 [thread overview]
Message-ID: <aeTOgEq9X192XPgG@valkosipuli.retiisi.eu> (raw)
In-Reply-To: <CAHp75VcyO4rJMyVyUP6aKLugEBik_FPsyO4cgbPkTgnKUzhG+A@mail.gmail.com>
Moi,
On Sun, Apr 19, 2026 at 11:32:45AM +0300, Andy Shevchenko wrote:
> On Sun, Apr 19, 2026 at 1:20 AM Sakari Ailus <sakari.ailus@iki.fi> wrote:
>
> > On Wed, Nov 26, 2025 at 07:00:26PM +0000, Ayush Kumar wrote:
> > > Adhering to Linux kernel coding style guidelines (Chapter 3: Indentation).
> > >
> > > Signed-off-by: Ayush Kumar <ayushkr0s@gmail.com>
> >
> > This has been addressed by commit 003c2c39ec77c84d704ee8effe170fd8658fde0b
> > in my atomisp branch.
>
> Btw, can you rebase your branch and drop "staging" word from the
> Subject in all current patches?
Good question. The staging: prefix has been used in the past for atomisp
patches and a lot of the rest appears to be doing that as well but
definitely not all. I don't really have an opinion but we should do that
consistently whichever is chosen.
--
Terveisin,
Sakari Ailus
prev parent reply other threads:[~2026-04-19 12:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 19:00 [PATCH] media: atomisp: coding style: Move trailing statements to next line Ayush Kumar
2025-11-26 19:32 ` Andy Shevchenko
2025-11-26 20:23 ` Greg KH
2026-04-18 22:20 ` Sakari Ailus
2026-04-19 8:32 ` Andy Shevchenko
2026-04-19 12:45 ` Sakari Ailus [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=aeTOgEq9X192XPgG@valkosipuli.retiisi.eu \
--to=sakari.ailus@iki.fi \
--cc=abdelrahmanfekry375@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=ayushkr0s@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=hverkuil@kernel.org \
--cc=kernel-newbies@vger.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=ribalda@chromium.org \
--cc=sakari.ailus@linux.intel.com \
--cc=santiagorr@riseup.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