From: Greg KH <gregkh@linuxfoundation.org>
To: Bogdan Sandu <bogdanelsandu2011@gmail.com>
Cc: sakari.ailus@linux.intel.com, bingbu.cao@intel.com,
tian.shu.qiu@intel.com, mchehab@kernel.org,
linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Cleanup ipu3 driver
Date: Mon, 2 Feb 2026 11:14:26 +0100 [thread overview]
Message-ID: <2026020258-very-numbly-b36b@gregkh> (raw)
In-Reply-To: <20260202100310.4425-2-bogdanelsandu2011@gmail.com>
On Mon, Feb 02, 2026 at 12:03:11PM +0200, Bogdan Sandu wrote:
> Clean up warnings generated by ./scripts/checkpatch.pl regarding the ipu3 driver at /drivers/staging/media/ipu3
>
> More specifically, the following files have been affected: ipu3-css.c, ipu3-mmu.c, ipu3-mmu.h, ipu3-v4l2.c, ipu3.c, ipu3.h
Was this an AI generated patch?
Either way, it needs to be properly broken up into "one logical change
per patch" like all others.
thanks,
greg k-h
next prev parent reply other threads:[~2026-02-02 10:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 10:03 [PATCH] Cleanup ipu3 driver Bogdan Sandu
2026-02-02 10:14 ` Greg KH [this message]
2026-02-02 10:18 ` [RE:PATCH] " Bogdan Sandu
2026-02-02 10:18 ` [PATCH] " Bogdan Sandu
2026-02-02 10:32 ` Greg KH
2026-02-02 10:34 ` Bogdan Sandu
2026-02-02 17:50 ` [PATCH v2 0/4] Cleanup media:ipu3 driver Bogdan Sandu
2026-02-02 17:50 ` [PATCH v2 1/4] media: ipu3: fix alignment Bogdan Sandu
2026-03-05 8:15 ` Sakari Ailus
2026-03-11 18:39 ` Bogdan Sandu
2026-02-02 17:50 ` [PATCH v2 2/4] media: ipu3: use tabs Bogdan Sandu
2026-03-05 8:16 ` Sakari Ailus
2026-02-02 17:50 ` [PATCH v2 3/4] media: ipu3: avoid ending lines with paranthesis Bogdan Sandu
2026-02-02 17:50 ` [PATCH v2 4/4] media: ipu3: use BIT() Bogdan Sandu
2026-02-02 20:08 ` Dan Carpenter
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=2026020258-very-numbly-b36b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bingbu.cao@intel.com \
--cc=bogdanelsandu2011@gmail.com \
--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 \
--cc=tian.shu.qiu@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