From: Edward Wu <edwardwu@realtek.com>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>, Hannes Reinecke <hare@suse.de>,
Edward Wu <edwardwu@realtek.com>, Tejun Heo <tj@kernel.org>,
<linux-ide@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <stable@vger.kernel.org>
Subject: [PATCH v4] ata: libata: add qc->flags in ata_qc_complete_template tracepoint
Date: Fri, 17 Jun 2022 11:32:20 +0800 [thread overview]
Message-ID: <20220617033221.22049-1-edwardwu@realtek.com> (raw)
In-Reply-To: <20220616001615.11636-1-edwardwu@realtek.com>
Add flags value to check the result of ata completion
Fixes: 255c03d15a29 ("libata: Add tracepoints")
Cc: stable@vger.kernel.org
Signed-off-by: Edward Wu <edwardwu@realtek.com>
---
Fixed, thanks again
include/trace/events/libata.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/trace/events/libata.h b/include/trace/events/libata.h
index d4e631aa976f..6025dd8ba4aa 100644
--- a/include/trace/events/libata.h
+++ b/include/trace/events/libata.h
@@ -288,6 +288,7 @@ DECLARE_EVENT_CLASS(ata_qc_complete_template,
__entry->hob_feature = qc->result_tf.hob_feature;
__entry->nsect = qc->result_tf.nsect;
__entry->hob_nsect = qc->result_tf.hob_nsect;
+ __entry->flags = qc->flags;
),
TP_printk("ata_port=%u ata_dev=%u tag=%d flags=%s status=%s " \
--
2.17.1
next prev parent reply other threads:[~2022-06-17 3:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 0:16 [PATCH] ata: libata: add qc->flags in ata_qc_complete_template tracepoint Edward Wu
2022-06-16 0:34 ` Damien Le Moal
2022-06-16 0:48 ` [PATCH v2] " Edward Wu
2022-06-16 2:55 ` Damien Le Moal
2022-06-17 3:00 ` [PATCH v3] " Edward Wu
2022-06-17 3:26 ` Damien Le Moal
2022-06-17 3:32 ` Edward Wu [this message]
2022-06-17 7:32 ` [PATCH v4] " Damien Le Moal
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=20220617033221.22049-1-edwardwu@realtek.com \
--to=edwardwu@realtek.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=hare@suse.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=tj@kernel.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