public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Asmaa Mnebhi <Asmaa@mellanox.com>
To: minyard@acm.org
Cc: Asmaa Mnebhi <Asmaa@mellanox.com>, linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/1] Fix uninitialized variable in ipmb_dev_int.c
Date: Wed, 24 Jul 2019 10:36:41 -0400	[thread overview]
Message-ID: <cover.1563978634.git.Asmaa@mellanox.com> (raw)

ret at line 112 of ipmb_dev_int.c is uninitialized which
results in a warning during build regressions.

Asmaa Mnebhi (1):
  Fix uninitialized variable in ipmb_dev_int.c

 drivers/char/ipmi/ipmb_dev_int.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
2.1.2


WARNING: multiple messages have this Message-ID (diff)
From: Asmaa Mnebhi <Asmaa@mellanox.com>
To: minyard@acm.org
Cc: Asmaa Mnebhi <Asmaa@mellanox.com>, linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/1] Fix uninitialized variable in ipmb_dev_int.c
Date: Wed, 24 Jul 2019 13:45:56 -0400	[thread overview]
Message-ID: <cover.1563978634.git.Asmaa@mellanox.com> (raw)
Message-ID: <20190724174556.LMyWwPUr-Vk0jsFYD27z0jBnVoYWplI-Pxs0zcewzdg@z> (raw)

ret at line 112 of ipmb_dev_int.c is uninitialized which
results in a warning during build regressions.

This warning was reported during regression testing led by Geert
Uytterhoeven for v5.3-rc1.

Asmaa Mnebhi (1):
  Fix uninitialized variable in ipmb_dev_int.c

 drivers/char/ipmi/ipmb_dev_int.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
2.1.2


             reply	other threads:[~2019-07-24 14:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-24 14:36 Asmaa Mnebhi [this message]
2019-07-24 14:36 ` [PATCH v1 1/1] Fix uninitialized variable in ipmb_dev_int.c Asmaa Mnebhi
2019-07-24 15:33   ` Corey Minyard
2019-07-24 17:45   ` Asmaa Mnebhi
2019-07-24 19:06   ` Corey Minyard
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

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=cover.1563978634.git.Asmaa@mellanox.com \
    --to=asmaa@mellanox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minyard@acm.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