From: Steven Rostedt <rostedt@goodmis.org>
To: Arun Easi <aeasi@marvell.com>
Cc: Daniel Wagner <dwagner@suse.de>,
Nilesh Javali <njavali@marvell.com>, <martin.petersen@oracle.com>,
<linux-scsi@vger.kernel.org>,
<GR-QLogic-Storage-Upstream@marvell.com>, <bhazarika@marvell.com>,
<agurumurthy@marvell.com>
Subject: Re: [EXT] Re: [PATCH 2/6] qla2xxx: Add a generic tracing framework
Date: Tue, 19 Jul 2022 18:17:16 -0400 [thread overview]
Message-ID: <20220719181716.107c6eb0@gandalf.local.home> (raw)
In-Reply-To: <782837dd-5eb2-c7dd-7cc1-25ca97806830@marvell.com>
On Tue, 19 Jul 2022 15:09:30 -0700
Arun Easi <aeasi@marvell.com> wrote:
> This will be nice.
>
> Thanks for your help, Steve.
No problem.
What a coincidence that I just finished this work earlier this month.
-- Steve
next prev parent reply other threads:[~2022-07-19 22:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 6:02 [PATCH 0/6] qla2xxx driver features Nilesh Javali
2022-07-15 6:02 ` [PATCH 1/6] qla2xxx: Add debugfs create/delete helpers Nilesh Javali
2022-07-15 6:02 ` [PATCH 2/6] qla2xxx: Add a generic tracing framework Nilesh Javali
2022-07-18 8:54 ` Daniel Wagner
2022-07-18 19:02 ` Arun Easi
2022-07-18 19:22 ` Steven Rostedt
2022-07-19 8:25 ` Daniel Wagner
2022-07-19 13:05 ` Steven Rostedt
2022-07-19 22:09 ` [EXT] " Arun Easi
2022-07-23 7:47 ` Steffen Maier
2022-07-25 13:56 ` Steven Rostedt
2022-07-19 21:06 ` Arun Easi
2022-07-19 21:40 ` Steven Rostedt
2022-07-19 22:09 ` Arun Easi
2022-07-19 22:17 ` Steven Rostedt [this message]
2022-07-20 4:43 ` kernel test robot
2022-07-15 6:02 ` [PATCH 3/6] qla2xxx: Add driver console messages tracing Nilesh Javali
2022-07-15 6:02 ` [PATCH 4/6] qla2xxx: Add srb tracing Nilesh Javali
2022-07-15 6:02 ` [PATCH 5/6] qla2xxx: Add NVMe parameters support in Auxiliary Image Status Nilesh Javali
2022-07-15 6:02 ` [PATCH 6/6] qla2xxx: Update version to 10.02.07.900-k Nilesh Javali
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=20220719181716.107c6eb0@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=GR-QLogic-Storage-Upstream@marvell.com \
--cc=aeasi@marvell.com \
--cc=agurumurthy@marvell.com \
--cc=bhazarika@marvell.com \
--cc=dwagner@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=njavali@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.