From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Edward Wu <edwardwu@realtek.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>, Hannes Reinecke <hare@suse.de>,
Tejun Heo <tj@kernel.org>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ata: libata: add qc->flags in ata_qc_complete_template tracepoint
Date: Thu, 16 Jun 2022 11:55:15 +0900 [thread overview]
Message-ID: <bcd06ab1-6ead-985b-eff8-cbc526a8aa84@opensource.wdc.com> (raw)
In-Reply-To: <20220616004803.12145-1-edwardwu@realtek.com>
On 6/16/22 09:48, Edward Wu wrote:
> Add flags value to check the result of ata completion
>
> Fixes: 255c03d15a29 ("libata: Add tracepoints")
> Link: https://lkml.kernel.org/r/20220616001615.11636-1-edwardwu@realtek.com
What is this Link tag for ? I do not think it is needed.
And please add:
Cc: stable@vger.kernel.org
> Signed-off-by: Edward Wu <edwardwu@realtek.com>
> ---
> v2:
> - Add Fixes tag
>
> 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 " \
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2022-06-16 2:55 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 [this message]
2022-06-17 3:00 ` [PATCH v3] " Edward Wu
2022-06-17 3:26 ` Damien Le Moal
2022-06-17 3:32 ` [PATCH v4] " Edward Wu
2022-06-17 7:32 ` 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=bcd06ab1-6ead-985b-eff8-cbc526a8aa84@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=edwardwu@realtek.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=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