From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "jg@lightnvm.io" <jg@lightnvm.io>
Cc: "mb@lightnvm.io" <mb@lightnvm.io>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH v5] lightnvn: pblk
Date: Tue, 11 Apr 2017 22:23:37 +0000 [thread overview]
Message-ID: <1491949415.2654.23.camel@sandisk.com> (raw)
In-Reply-To: <8123618D-0CBB-420B-BC68-64A0A36E2532@lightnvm.io>
On Wed, 2017-04-12 at 00:13 +0200, Javier Gonz=E1lez wrote:
> please point out to any other tools/concerns you may have.
Hello Javier,
Do you already have an account at https://scan.coverity.com/? Any Linux
kernel developer can get an account for free. A full Coverity scan of
Linus' tree is available at https://scan.coverity.com/projects/linux.
Bart.=
next prev parent reply other threads:[~2017-04-11 22:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 14:31 [PATCH v5] lightnvn: pblk Javier González
[not found] ` <1491921077-9377-2-git-send-email-javier@cnexlabs.com>
2017-04-11 14:41 ` [PATCH v5] lightnvm: physical block device (pblk) target Matias Bjørling
2017-04-11 15:19 ` [PATCH v5] lightnvn: pblk Bart Van Assche
2017-04-11 22:13 ` Javier González
2017-04-11 22:23 ` Bart Van Assche [this message]
2017-04-12 8:04 ` Javier González
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=1491949415.2654.23.camel@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=jg@lightnvm.io \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@lightnvm.io \
/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