From: Dan Carpenter <dan.carpenter@oracle.com>
To: Anant Thazhemadam <anant.thazhemadam@gmail.com>
Cc: devel@driverdev.osuosl.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org
Subject: Re: [PATCH] staging: media-atomisp : fix "dubious: !x | !y" sparse warning
Date: Wed, 26 Aug 2020 12:50:00 +0300 [thread overview]
Message-ID: <20200826095000.GW1793@kadam> (raw)
In-Reply-To: <20200825220437.11214-1-anant.thazhemadam@gmail.com>
On Wed, Aug 26, 2020 at 03:34:26AM +0530, Anant Thazhemadam wrote:
> Upon running sparse, "warning: dubious: !x | !y" is brought to notice
> for this file. This patch fixes that warning.
>
> If there's a specific reason that this change is considered undesirable,
> please do let me know why.
> Thanks.
Please don't put this sort of comments in the commit message. You can
put it under the --- cut off
>
> Signed-off-by: Anant Thazhemadam <anant.thazhemadam@gmail.com>
> ---
^^^
here. Then it will be removed instead of going into the permanent git
log.
Please always say int the commit message how the patch will affect the
runtime behavior of the kernel. In this case it will not affect it at
all. It's just a clean up. Her is my proposed commit message if you
want:
Subject: [PATCH] staging: media-atomisp : silence "dubious: !x | !y" warning
Upon running sparse, "warning: dubious: !x | !y" is brought to notice
for this file. Logical and bitwise OR are basically the same in this
context so it doesn't cause a runtime bug. But let's change it to
logical OR to make it cleaner and silence the Sparse warning.
regards,
dan carpenter
> .../media/atomisp/pci/isp/kernels/vf/vf_1.0/ia_css_vf.host.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/media/atomisp/pci/isp/kernels/vf/vf_1.0/ia_css_vf.host.c b/drivers/staging/media/atomisp/pci/isp/kernels/vf/vf_1.0/ia_css_vf.host.c
> index 358cb7d2cd4c..3b850bb2d39d 100644
> --- a/drivers/staging/media/atomisp/pci/isp/kernels/vf/vf_1.0/ia_css_vf.host.c
> +++ b/drivers/staging/media/atomisp/pci/isp/kernels/vf/vf_1.0/ia_css_vf.host.c
> @@ -58,7 +58,7 @@ sh_css_vf_downscale_log2(
> unsigned int ds_log2 = 0;
> unsigned int out_width;
>
> - if ((!out_info) | (!vf_info))
> + if ((!out_info) || (!vf_info))
> return -EINVAL;
>
> out_width = out_info->res.width;
> --
> 2.25.1
>
> _______________________________________________
> devel mailing list
> devel@linuxdriverproject.org
> http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2020-08-26 9:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 22:04 [PATCH] staging: media-atomisp : fix "dubious: !x | !y" sparse warning Anant Thazhemadam
2020-08-26 9:50 ` Dan Carpenter [this message]
2020-08-26 11:09 ` [PATCH v2] staging: media/atomisp " Anant Thazhemadam
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=20200826095000.GW1793@kadam \
--to=dan.carpenter@oracle.com \
--cc=anant.thazhemadam@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--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