From: Sagi Grimberg <sagi@grimberg.me>
To: kernel test robot <lkp@intel.com>, Hannes Reinecke <hare@suse.de>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@lst.de>,
Chaitanya Kulkarni <kch@nvidia.com>,
Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvme-fabrics: fix returnvar.cocci warnings
Date: Sun, 23 Jan 2022 11:16:53 +0200 [thread overview]
Message-ID: <aa0e01c1-4d3e-eed2-d32f-d1ecb9a97e90@grimberg.me> (raw)
In-Reply-To: <20220122031737.GA31599@fba2a898af35>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
next prev parent reply other threads:[~2022-01-23 9:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 3:26 drivers/nvme/host/fabrics.c:1095:5-8: Unneeded variable: "ret". Return "0" on line 1109 kernel test robot
2022-01-22 3:17 ` [PATCH] nvme-fabrics: fix returnvar.cocci warnings kernel test robot
2022-01-22 4:27 ` Chaitanya Kulkarni
2022-01-23 9:16 ` Sagi Grimberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-23 1:04 drivers/nvme/host/fabrics.c:1095:5-8: Unneeded variable: "ret". Return "0" on line 1109 kernel test robot
2022-04-23 1:00 ` [PATCH] nvme-fabrics: fix returnvar.cocci warnings kernel test robot
2022-01-25 19:16 drivers/nvme/host/fabrics.c:1095:5-8: Unneeded variable: "ret". Return "0" on line 1109 kernel test robot
2022-01-25 16:12 ` [PATCH] nvme-fabrics: fix returnvar.cocci warnings kernel test robot
2022-01-18 11:13 drivers/nvme/host/fabrics.c:1095:5-8: Unneeded variable: "ret". Return "0" on line 1109 kernel test robot
2022-01-18 9:25 ` [PATCH] nvme-fabrics: fix returnvar.cocci warnings kernel test robot
2022-01-19 7:40 ` Chaitanya Kulkarni
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=aa0e01c1-4d3e-eed2-d32f-d1ecb9a97e90@grimberg.me \
--to=sagi@grimberg.me \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbuild-all@lists.01.org \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=lkp@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;
as well as URLs for NNTP newsgroup(s).