mirror of https://lore.kernel.org/lkml/
 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/8] firewire: store the numeric identifier of card in data structure for tracepoint events
Date: Sat, 15 Jun 2024 15:01:43 +0900	[thread overview]
Message-ID: <20240615060143.GB497879@workstation.local> (raw)
In-Reply-To: <20240613131440.431766-1-o-takashi@sakamocchi.jp>

On Thu, Jun 13, 2024 at 10:14:32PM +0900, Takashi Sakamoto wrote:
> Hi,
> 
> In v6.10 kernel, some tracepoints events are added to record
> IEEE 1394 asynchronous communication. In the case that multiple 1394 OHCI
> controllers are available in Linux system, it is hard to distinguish
> the controller used for the communication, since these events have no
> member in their data structure to express the used controller. It is a
> bit inconvenient to diagnose things.
> 
> This series of patches is an attempt to solve the issue. In Linux
> FireWire core, the available controllers are maintained in list, and
> each of them has its own numeric identifier (=card_index). In this
> series, the index value is added to the data structure.
> 
> I would like to put the change to v6.10-rc4 (or later) as the part of
> fixes if receiving no objections.
> 
> Takashi Sakamoto (8):
>   firewire: core: record card index in tracepoinrts events derived from
>     async_outbound_complete_template
>   firewire: core: record card index in tracepoinrts events derived from
>     async_outbound_initiate_template
>   firewire: core: record card index in tracepoinrts events derived from
>     async_inbound_template
>   firewire: core: record card index in async_phy_outbound_initiate
>     tracepoints event
>   firewire: core: record card index in async_phy_outbound_complete
>     tracepoints event
>   firewire: core: record card index in async_phy_inbound tracepoints
>     event
>   firewire: core: record card index in tracepoinrts events derived from
>     bus_reset_arrange_template
>   firewire: core: record card index in bus_reset_handle tracepoints
>     event
> 
>  drivers/firewire/core-card.c        |   6 +-
>  drivers/firewire/core-cdev.c        |   6 +-
>  drivers/firewire/core-topology.c    |   2 +-
>  drivers/firewire/core-transaction.c |  30 ++++----
>  include/trace/events/firewire.h     | 113 +++++++++++++++++-----------
>  5 files changed, 92 insertions(+), 65 deletions(-)

Applied to for-linus branch.


Thanks

Takashi Sakamoto

      parent reply	other threads:[~2024-06-15  6:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13 13:14 Takashi Sakamoto
2024-06-13 13:14 ` [PATCH 1/8] firewire: core: record card index in tracepoinrts events derived from async_outbound_complete_template Takashi Sakamoto
2024-06-13 13:14 ` [PATCH 2/8] firewire: core: record card index in tracepoinrts events derived from async_outbound_initiate_template Takashi Sakamoto
2024-06-13 13:14 ` [PATCH 3/8] firewire: core: record card index in tracepoinrts events derived from async_inbound_template Takashi Sakamoto
2024-06-13 13:14 ` [PATCH 4/8] firewire: core: record card index in async_phy_outbound_initiate tracepoints event Takashi Sakamoto
2024-06-13 13:14 ` [PATCH 5/8] firewire: core: record card index in async_phy_outbound_complete " Takashi Sakamoto
2024-06-13 13:14 ` [PATCH 6/8] firewire: core: record card index in async_phy_inbound " Takashi Sakamoto
2024-06-13 13:14 ` [PATCH 7/8] firewire: core: record card index in tracepoinrts events derived from bus_reset_arrange_template Takashi Sakamoto
2024-06-13 13:14 ` [PATCH 8/8] firewire: core: record card index in bus_reset_handle tracepoints event Takashi Sakamoto
2024-06-15  6:01 ` 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=20240615060143.GB497879@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

all inboxes | Powered by JetHome®