From: Jacob Keller <jacob.e.keller@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH 0/4] devlink region snapshot triggering
Date: Thu, 9 Jan 2020 10:48:26 -0800 [thread overview]
Message-ID: <c342b0c0-96e0-73fa-43b9-5544ec5195a9@intel.com> (raw)
In-Reply-To: <20200109070051.GA2235@nanopsycho.orion>
On 1/8/2020 11:00 PM, Jiri Pirko wrote:
> Thu, Jan 09, 2020 at 02:08:15AM CET, jacob.e.keller at intel.com wrote:
>> There is also some fix ups for s/shapshot/snapshot/ in documentation
>> and the devlink_snapshot_id_get function.
>
> You can already trigger health reporter dump from userspace. Why don't
> you use health reporter?
>
Hmm. Mainly because the specific things I wanted to expose through
regions aren't really "health" information.
Thanks,
Jake
next prev parent reply other threads:[~2020-01-09 18:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 1:08 [Intel-wired-lan] [PATCH 0/4] devlink region snapshot triggering Jacob Keller
2020-01-09 1:08 ` [Intel-wired-lan] [PATCH 1/4] devlink: correct misspelling of snapshot Jacob Keller
2020-01-09 1:08 ` [Intel-wired-lan] [PATCH 2/4] doc: fix typo of snapshot in documentation Jacob Keller
2020-01-09 7:01 ` Jiri Pirko
2020-01-09 1:08 ` [Intel-wired-lan] [PATCH 3/4] devlink: add support for triggering snapshots from userspace Jacob Keller
2020-01-09 7:05 ` Jiri Pirko
2020-01-09 18:50 ` Jacob Keller
2020-01-09 18:58 ` Jiri Pirko
2020-01-09 19:07 ` Jacob Keller
2020-01-09 19:35 ` Jacob Keller
2020-01-09 1:08 ` [Intel-wired-lan] [PATCH 4/4] devlink: add support for DEVLINK_CMD_REGION_TRIGGER_SNAPSHOT Jacob Keller
2020-01-09 7:00 ` [Intel-wired-lan] [PATCH 0/4] devlink region snapshot triggering Jiri Pirko
2020-01-09 18:48 ` Jacob Keller [this message]
2020-01-09 18:59 ` Jiri Pirko
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=c342b0c0-96e0-73fa-43b9-5544ec5195a9@intel.com \
--to=jacob.e.keller@intel.com \
--cc=intel-wired-lan@osuosl.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