From: sashiko-bot@kernel.org
To: "Link Mauve" <linkmauve@linkmauve.fr>
Cc: imx@lists.linux.dev, linux-amlogic@lists.infradead.org,
linux-sunxi@lists.linux.dev,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
mfd@lists.linux.dev, ojeda@kernel.org, neil.armstrong@linaro.org,
linux-rtc@vger.kernel.org, Frank.Li@kernel.org, lee@kernel.org
Subject: Re: [PATCH 8/8] media: ov2740: remove NULL reg_write callback
Date: Wed, 15 Jul 2026 18:07:34 +0000 [thread overview]
Message-ID: <20260715180734.91AE41F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260715175229.24672-9-linkmauve@linkmauve.fr>
> This field is already initialized to NULL, so there is no reason to
> write it again.
>
> This prevents it from appearing while grepping for reg_write in the
> future.
>
> Signed-off-by: Link Mauve <linkmauve@linkmauve.fr>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260715175229.24672-1-linkmauve@linkmauve.fr?part=8
WARNING: multiple messages have this Message-ID (diff)
From: sashiko-bot@kernel.org
To: "Link Mauve" <linkmauve@linkmauve.fr>
Cc: imx@lists.linux.dev, linux-amlogic@lists.infradead.org,
linux-sunxi@lists.linux.dev,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
mfd@lists.linux.dev, ojeda@kernel.org, neil.armstrong@linaro.org,
linux-rtc@vger.kernel.org, Frank.Li@kernel.org, lee@kernel.org
Subject: Re: [PATCH 8/8] media: ov2740: remove NULL reg_write callback
Date: Wed, 15 Jul 2026 18:07:34 +0000 [thread overview]
Message-ID: <20260715180734.91AE41F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260715175229.24672-9-linkmauve@linkmauve.fr>
> This field is already initialized to NULL, so there is no reason to
> write it again.
>
> This prevents it from appearing while grepping for reg_write in the
> future.
>
> Signed-off-by: Link Mauve <linkmauve@linkmauve.fr>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260715175229.24672-1-linkmauve@linkmauve.fr?part=8
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2026-07-15 18:07 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 17:52 [PATCH 0/8] nvmem: make reg_write() take a const void * Link Mauve
2026-07-15 17:52 ` Link Mauve
2026-07-15 17:52 ` [PATCH 1/8] nvmem: core: " Link Mauve
2026-07-15 17:52 ` Link Mauve
2026-07-15 18:00 ` sashiko-bot
2026-07-15 18:00 ` sashiko-bot
2026-07-15 18:58 ` Andy Shevchenko
2026-07-15 18:58 ` Andy Shevchenko
2026-07-15 19:03 ` Link Mauve
2026-07-15 19:03 ` Link Mauve
2026-07-15 17:52 ` [PATCH 2/8] nvmem: make all reg_write callbacks take " Link Mauve
2026-07-15 17:52 ` Link Mauve
2026-07-15 18:08 ` sashiko-bot
2026-07-15 18:08 ` sashiko-bot
2026-07-15 17:52 ` [PATCH 3/8] rtc: " Link Mauve
2026-07-15 17:52 ` Link Mauve
2026-07-15 18:01 ` sashiko-bot
2026-07-15 18:01 ` sashiko-bot
2026-07-15 17:52 ` [PATCH 4/8] misc: " Link Mauve
2026-07-15 17:52 ` Link Mauve
2026-07-15 18:04 ` sashiko-bot
2026-07-15 18:04 ` sashiko-bot
2026-07-15 17:52 ` [PATCH 5/8] iio: pressure: bmp280: make reg_write callback " Link Mauve
2026-07-15 17:52 ` Link Mauve
2026-07-15 18:03 ` sashiko-bot
2026-07-15 18:03 ` sashiko-bot
2026-07-15 17:52 ` [PATCH 6/8] firmware: meson_sm: " Link Mauve
2026-07-15 17:52 ` Link Mauve
2026-07-15 18:06 ` sashiko-bot
2026-07-15 18:06 ` sashiko-bot
2026-07-15 17:52 ` [PATCH 7/8] mfd: twl-core: " Link Mauve
2026-07-15 17:52 ` Link Mauve
2026-07-15 18:08 ` sashiko-bot
2026-07-15 18:08 ` sashiko-bot
2026-07-15 17:52 ` [PATCH 8/8] media: ov2740: remove NULL reg_write callback Link Mauve
2026-07-15 17:52 ` Link Mauve
2026-07-15 18:07 ` sashiko-bot [this message]
2026-07-15 18:07 ` sashiko-bot
2026-07-15 19:02 ` [PATCH 0/8] nvmem: make reg_write() take a const void * Andy Shevchenko
2026-07-15 19:02 ` Andy Shevchenko
2026-07-15 19:09 ` Link Mauve
2026-07-15 19:09 ` Link Mauve
2026-07-15 20:09 ` Yury Norov
2026-07-15 20:09 ` Yury Norov
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=20260715180734.91AE41F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=imx@lists.linux.dev \
--cc=lee@kernel.org \
--cc=linkmauve@linkmauve.fr \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mfd@lists.linux.dev \
--cc=neil.armstrong@linaro.org \
--cc=ojeda@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.