From: Walker, Benjamin <benjamin.walker at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] gdb macros
Date: Mon, 28 Jan 2019 16:42:20 +0000 [thread overview]
Message-ID: <d38e76119d6a58b8d48542b2dcbcdcc17d8ee20f.camel@intel.com> (raw)
In-Reply-To: VI1PR04MB5134FBBD07730AF693566DD089960@VI1PR04MB5134.eurprd04.prod.outlook.com
[-- Attachment #1: Type: text/plain, Size: 889 bytes --]
On Mon, 2019-01-28 at 14:44 +0000, Shahar Salzman wrote:
> For some reason jenkins failed with a link to a page with http error 404.
> Not sure of the reason, this code doesn't go in any test/lib, and I ran the
> check_format.sh tool before I did my local commit...
>
> Posted the code for review:
> https://review.gerrithub.io/c/spdk/spdk/+/442325
>
> I know that there is a ton of additional information which can be shown for
> these objects.
> I currently implemented what was useful to me, I will probably add some more
> later on when other needs arise, but this should be a nice starting point.
Thanks so much for writing these! I'm going to pick up the discussion as
comments on that code review. I think tooling like this is absolutely invaluable
to SPDK (and it really shows how much easier it is to program in user space than
in the kernel).
Thanks,
Ben
next reply other threads:[~2019-01-28 16:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 16:42 Walker, Benjamin [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-28 16:02 [SPDK] gdb macros Luse, Paul E
2019-01-28 14:44 Shahar Salzman
2019-01-28 14:39 Shahar Salzman
2019-01-28 5:16 Cao, Gang
2019-01-27 12:47 Shahar Salzman
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=d38e76119d6a58b8d48542b2dcbcdcc17d8ee20f.camel@intel.com \
--to=spdk@lists.01.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