From: Corey Minyard <minyard@acm.org>
To: Asmaa Mnebhi <Asmaa@mellanox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] Fix uninitialized variable in ipmb_dev_int.c
Date: Wed, 24 Jul 2019 14:06:40 -0500 [thread overview]
Message-ID: <20190724190640.GK3066@minyard.net> (raw)
In-Reply-To: <84ef25695b2bfa5100803d5bb30e5d4152e336e0.1563978634.git.Asmaa@mellanox.com>
On Wed, Jul 24, 2019 at 01:45:57PM -0400, Asmaa Mnebhi wrote:
> Signed-off-by: Asmaa Mnebhi <Asmaa@mellanox.com>
> Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
Sorry to be picky here, but it's considered bad style to have an
empty message. I probably wasn't clear before, but you should
add some text like "Found by build regression/improvement testing."
or something like that. Just so people know where it was found.
Could you also add a "Fixes" field? This is important in case
someone pulls the original patch, they can look forward and see
if any bugs were fixed. From the kernel docs:
If your patch fixes a bug in a specific commit, e.g. you found an issue using
``git bisect``, please use the 'Fixes:' tag with the first 12 characters of
the SHA-1 ID, and the one line summary. Do not split the tag across multiple
lines, tags are exempt from the "wrap at 75 columns" rule in order to simplify
parsing scripts. For example::
Fixes: 54a4f0239f2e ("KVM: MMU: make kvm_mmu_zap_page() return the number of pages it actually freed")
I was going to do that myself, but since another spin is required...
Thanks,
-corey
> ---
> drivers/char/ipmi/ipmb_dev_int.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/char/ipmi/ipmb_dev_int.c b/drivers/char/ipmi/ipmb_dev_int.c
> index 5720433..285e0b8 100644
> --- a/drivers/char/ipmi/ipmb_dev_int.c
> +++ b/drivers/char/ipmi/ipmb_dev_int.c
> @@ -76,7 +76,7 @@ static ssize_t ipmb_read(struct file *file, char __user *buf, size_t count,
> struct ipmb_dev *ipmb_dev = to_ipmb_dev(file);
> struct ipmb_request_elem *queue_elem;
> struct ipmb_msg msg;
> - ssize_t ret;
> + ssize_t ret = 0;
>
> memset(&msg, 0, sizeof(msg));
>
> --
> 2.1.2
>
next prev parent reply other threads:[~2019-07-24 19:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 14:36 [PATCH v1 0/1] Fix uninitialized variable in ipmb_dev_int.c Asmaa Mnebhi
2019-07-24 14:36 ` [PATCH v1 1/1] " Asmaa Mnebhi
2019-07-24 15:33 ` Corey Minyard
2019-07-24 17:45 ` Asmaa Mnebhi
2019-07-24 19:06 ` Corey Minyard [this message]
2019-07-24 19:09 ` Asmaa Mnebhi
2019-07-24 17:45 ` [PATCH v1 0/1] " Asmaa Mnebhi
-- strict thread matches above, loose matches on Subject: below --
2019-07-24 19:32 Asmaa Mnebhi
2019-07-24 19:32 ` [PATCH v1 1/1] " Asmaa Mnebhi
2019-07-24 20:53 ` Corey Minyard
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=20190724190640.GK3066@minyard.net \
--to=minyard@acm.org \
--cc=Asmaa@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
/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