From: Dan Carpenter <dan.carpenter@linaro.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Colin Ian King <colin.i.king@gmail.com>,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-media@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] media: i2c: ds90ub960: Fix missing return check on ub960_rxport_read call
Date: Wed, 16 Oct 2024 16:39:54 +0300 [thread overview]
Message-ID: <18412b95-7d34-4a80-940b-e5fc5bec3ec9@stanley.mountain> (raw)
In-Reply-To: <20241016094111.7f5e899a@foz.lan>
On Wed, Oct 16, 2024 at 09:41:11AM +0200, Mauro Carvalho Chehab wrote:
> Em Wed, 2 Oct 2024 17:53:29 +0100
> Colin Ian King <colin.i.king@gmail.com> escreveu:
>
> > The function ub960_rxport_read is being called and afterwards ret is
> > being checked for any failures, however ret is not being assigned to
> > the return of the function call. Fix this by assigning ret to the
> > return of the call which appears to be missing.
> >
> > Fixes: afe267f2d368 ("media: i2c: add DS90UB960 driver")
> > Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
>
> No Cc: stable. Please follow the submission rules for fixes as stated
> at:
> Documentation/process/stable-kernel-rules.rst
>
> In summary, all patches containing fixes shall have a Cc stable. There
> are rules there for the very few exceptions where a patch is not meant
> to be backported:
>
> Cc: <stable+noautosel@kernel.org> # reason goes here, and must be present
>
I don't think this patch belongs in stable. It's doesn't fix a real life bug,
it's just static checker stuff. I also don't think we should forbid it from
going to stable if it's required as a dependency to backport a different patch.
regards,
dan carpenter
prev parent reply other threads:[~2024-10-16 13:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 16:53 Colin Ian King
2024-10-03 6:05 ` Sakari Ailus
2024-10-03 12:52 ` Tomi Valkeinen
2024-10-03 13:19 ` Sakari Ailus
2024-10-03 13:33 ` Tomi Valkeinen
2024-10-03 15:13 ` Sakari Ailus
2024-10-04 15:11 ` Tomi Valkeinen
2024-10-16 7:41 ` Mauro Carvalho Chehab
2024-10-16 13:39 ` Dan Carpenter [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=18412b95-7d34-4a80-940b-e5fc5bec3ec9@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=colin.i.king@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tomi.valkeinen@ideasonboard.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
all inboxes | Powered by JetHome®