All of lore.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 0/2] firewire: core/cdev: add tracepoints events for asynchronous phy packet
Date: Tue, 30 Apr 2024 22:11:00 +0900	[thread overview]
Message-ID: <20240430131100.GA7699@workstation.local> (raw)
In-Reply-To: <20240430001404.734657-1-o-takashi@sakamocchi.jp>

On Tue, Apr 30, 2024 at 09:14:02AM +0900, Takashi Sakamoto wrote:
> Hi,
> 
> In IEEE 1394 bus, the type of asynchronous packet without any offset to
> node address space is called as phy packet. The destination of packet is
> IEEE 1394 phy itself. This type of packet is used for several purposes,
> mainly for selfID at the state of bus reset, to force selection of root
> node, and to adjust gap count.
> 
> This series of changes is to add tracepoints events for this kind of
> asynchronous packets.
> 
> Takashi Sakamoto (2):
>   firewire: core/cdev: add tracepoints events for asynchronous phy
>     packet
>   firewire: core: add tracepoints event for asynchronous inbound phy
>     packet
> 
>  drivers/firewire/core-cdev.c        |  7 +++
>  drivers/firewire/core-transaction.c |  8 +++
>  include/trace/events/firewire.h     | 78 +++++++++++++++++++++++++++++
>  3 files changed, 93 insertions(+)

Applied to for-next branch.


Regards

Takashi Sakamoto

      parent reply	other threads:[~2024-04-30 13:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-30  0:14 [PATCH 0/2] firewire: core/cdev: add tracepoints events for asynchronous phy packet Takashi Sakamoto
2024-04-30  0:14 ` [PATCH 1/2] " Takashi Sakamoto
2024-04-30  0:14 ` [PATCH 2/2] firewire: core: add tracepoints event for asynchronous inbound " Takashi Sakamoto
2024-04-30 13:11 ` Takashi Sakamoto [this message]

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=20240430131100.GA7699@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 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.