From: Dan Carpenter <dan.carpenter@oracle.com>
To: Norbert Manthey <norbertmanthey@googlemail.com>
Cc: nmanthey@amazon.de, smatch@vger.kernel.org, jsteckli@amazon.com,
tautschn@amazon.co.uk
Subject: Re: Smatch for Xen
Date: Mon, 6 Aug 2018 16:54:09 +0300 [thread overview]
Message-ID: <20180806135409.r5xytcrffqi3ddco@mwanda> (raw)
In-Reply-To: <CAByO1we3OABkX8XCwh7Vq8iHyXAuFtJ3t+Ta3DVCLe9pP6K8ew@mail.gmail.com>
On Mon, Aug 06, 2018 at 03:27:11PM +0200, Norbert Manthey wrote:
> Thanks a lot. I am currently out of the office, and might be able to
> respond once in a while. If required, I coukd get more details to help you
> by pulling in colleagues.
>
> If you have anything that i could improve wrt one-line-scan, please let me
> know.
>
The --file-output option seems to be broken for xen, but it's also
unnecessary if you're using one-line-scan because the output is already
separated by file.
What would help me is if the strored files like:
SMATCH/smatch/results/xen_arch_x86_pv_ro-page-fault.c
only store stdout and not stderr.
Of course, you'd prefer to not have any stderr output, but otherwise I'm
not interested in it. It just corrupts my stdout lines.
regards,
dan carpenter
next prev parent reply other threads:[~2018-08-06 16:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 12:40 Smatch for Xen Norbert Manthey
2018-07-30 16:34 ` [PATCH 0/3] add support for mode __pointer__ & __byte__ Luc Van Oostenryck
2018-07-30 16:34 ` [PATCH 1/3] mode keywords don't need MOD_{CHAR,LONG,...} Luc Van Oostenryck
2018-07-30 16:34 ` [PATCH 2/3] add support for mode __pointer__ Luc Van Oostenryck
2018-07-30 16:34 ` [PATCH 3/3] add support for mode __byte__ Luc Van Oostenryck
2018-08-06 10:31 ` Smatch for Xen Dan Carpenter
2018-08-06 11:20 ` Dan Carpenter
2018-08-06 13:16 ` Dan Carpenter
[not found] ` <CAByO1we3OABkX8XCwh7Vq8iHyXAuFtJ3t+Ta3DVCLe9pP6K8ew@mail.gmail.com>
2018-08-06 13:54 ` Dan Carpenter [this message]
2018-08-13 14:25 ` Norbert Manthey
2018-08-13 17:58 ` Dan Carpenter
2018-08-13 18:31 ` Dan Carpenter
2018-08-14 13:27 ` Norbert Manthey
2018-08-14 14:21 ` Dan Carpenter
2018-08-14 14:33 ` Norbert Manthey
2018-08-14 14:52 ` Dan Carpenter
2018-08-14 15:05 ` Norbert Manthey
2018-08-15 9:03 ` Dan Carpenter
2018-08-15 13:44 ` Norbert Manthey
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=20180806135409.r5xytcrffqi3ddco@mwanda \
--to=dan.carpenter@oracle.com \
--cc=jsteckli@amazon.com \
--cc=nmanthey@amazon.de \
--cc=norbertmanthey@googlemail.com \
--cc=smatch@vger.kernel.org \
--cc=tautschn@amazon.co.uk \
/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