public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: linux1394-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firewire: core: remove flag and width from u64 formats of tracepoints events
Date: Wed, 8 May 2024 18:54:36 +0900	[thread overview]
Message-ID: <20240508095436.GB433207@workstation.local> (raw)
In-Reply-To: <20240506082154.396077-2-o-takashi@sakamocchi.jp>

On Mon, May 06, 2024 at 05:21:54PM +0900, Takashi Sakamoto wrote:
> The pointer to fw_packet structure is passed to ring buffer of tracepoints
> framework as the value of u64 type. '0x%016llx' is used for the print
> format of value, while the flag and width are useless in the case.
> 
> This commit removes them.
> 
> Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>
> ---
>  include/trace/events/firewire.h | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/include/trace/events/firewire.h b/include/trace/events/firewire.h
> index 4163959be57a..cd6931b134ee 100644
> --- a/include/trace/events/firewire.h
> +++ b/include/trace/events/firewire.h
> @@ -221,7 +221,7 @@ TRACE_EVENT(async_phy_outbound_initiate,
>  		__entry->second_quadlet = second_quadlet
>  	),
>  	TP_printk(
> -		"packet=0x%016llx generation=%u first_quadlet=0x%08x second_quadlet=0x%08x",
> +		"packet=0x%llx generation=%u first_quadlet=0x%08x second_quadlet=0x%08x",
>  		__entry->packet,
>  		__entry->generation,
>  		__entry->first_quadlet,
> @@ -245,7 +245,7 @@ TRACE_EVENT(async_phy_outbound_complete,
>  		__entry->timestamp = timestamp;
>  	),
>  	TP_printk(
> -		"packet=0x%016llx generation=%u status=%u timestamp=0x%04x",
> +		"packet=0x%llx generation=%u status=%u timestamp=0x%04x",
>  		__entry->packet,
>  		__entry->generation,
>  		__entry->status,
> @@ -273,7 +273,7 @@ TRACE_EVENT(async_phy_inbound,
>  		__entry->second_quadlet = second_quadlet
>  	),
>  	TP_printk(
> -		"packet=0x%016llx generation=%u status=%u timestamp=0x%04x first_quadlet=0x%08x second_quadlet=0x%08x",
> +		"packet=0x%llx generation=%u status=%u timestamp=0x%04x first_quadlet=0x%08x second_quadlet=0x%08x",
>  		__entry->packet,
>  		__entry->generation,
>  		__entry->status,
> -- 
> 2.43.0

Applied to for-next branch.


Regards

Takashi Sakamoto

  reply	other threads:[~2024-05-08  9:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06  8:21 [PATCH] firewire: core: fix type of timestamp for async_inbound_template tracepoints events Takashi Sakamoto
2024-05-06  8:21 ` [PATCH] firewire: core: remove flag and width from u64 formats of " Takashi Sakamoto
2024-05-08  9:54   ` Takashi Sakamoto [this message]
2024-05-08  9:54 ` [PATCH] firewire: core: fix type of timestamp for async_inbound_template " Takashi Sakamoto

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=20240508095436.GB433207@workstation.local \
    --to=o-takashi@sakamocchi.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    /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