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 0/7] firewire: core: add tracepoints events for isochronous context
Date: Tue, 25 Jun 2024 07:35:03 +0900	[thread overview]
Message-ID: <20240624223503.GA914180@workstation.local> (raw)
In-Reply-To: <20240623220859.851685-1-o-takashi@sakamocchi.jp>

On Mon, Jun 24, 2024 at 07:08:51AM +0900, Takashi Sakamoto wrote:
> Hi,
> 
> It is helpful to trace any operation for isochronous context for
> debugging purposes. This series of changes is the last part to add
> tracepoints events into core function.
> 
> Takashi Sakamoto (7):
>   firewire: core: add tracepoints events for allocation/deallocation of
>     isochronous context
>   firewire: core: add tracepoints events for setting channels of
>     multichannel context
>   firewire: core: add tracepoints events for starting/stopping of
>     isochronous context
>   firewire: core: add tracepoints events for flushing of isochronous
>     context
>   firewire: core: add tracepoints events for flushing completions of
>     isochronous context
>   firewire: core: add tracepoints events for queueing packets of
>     isochronous context
>   firewire: core: add tracepoints events for completions of packets in
>     isochronous context
> 
>  drivers/firewire/core-iso.c     |  32 +++
>  drivers/firewire/core-trace.c   |   4 +
>  drivers/firewire/ohci.c         |  25 +-
>  include/trace/events/firewire.h | 463 ++++++++++++++++++++++++++++++++
>  4 files changed, 518 insertions(+), 6 deletions(-)

Applied to for-next branch.

Regards

Takashi Sakamoto

      parent reply	other threads:[~2024-06-24 22:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-23 22:08 [PATCH 0/7] firewire: core: add tracepoints events for isochronous context Takashi Sakamoto
2024-06-23 22:08 ` [PATCH 1/7] firewire: core: add tracepoints events for allocation/deallocation of " Takashi Sakamoto
2024-06-23 22:08 ` [PATCH 2/7] firewire: core: add tracepoints events for setting channels of multichannel context Takashi Sakamoto
2024-06-23 22:08 ` [PATCH 3/7] firewire: core: add tracepoints events for starting/stopping of isochronous context Takashi Sakamoto
2024-06-23 22:08 ` [PATCH 4/7] firewire: core: add tracepoints events for flushing " Takashi Sakamoto
2024-06-23 22:08 ` [PATCH 5/7] firewire: core: add tracepoints events for flushing completions " Takashi Sakamoto
2024-06-23 22:08 ` [PATCH 6/7] firewire: core: add tracepoints events for queueing packets " Takashi Sakamoto
2024-06-23 22:08 ` [PATCH 7/7] firewire: core: add tracepoints events for completions of packets in " Takashi Sakamoto
2024-06-24 22:35 ` 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=20240624223503.GA914180@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