public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux1394-devel@lists.sourceforge.net
Subject: [GIT PULL] firewire fixes for v6.18-rc3
Date: Sat, 25 Oct 2025 19:41:52 +0900	[thread overview]
Message-ID: <20251025104152.GA501617@workstation.local> (raw)

Hi Linus,

Please apply the following fixes to your tree for FireWire subsystem.


The following changes since commit 211ddde0823f1442e4ad052a2f30f050145ccada:

  Linux 6.18-rc2 (2025-10-19 15:19:16 -1000)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394.git tags/firewire-fixes-6.18-rc3

for you to fetch changes up to 73ba88fb04081372a69f0395958ac6b65d53d134:

  firewire: init_ohci1394_dma: add missing function parameter documentation (2025-10-25 08:29:56 +0900)

----------------------------------------------------------------
firewire fixes for 6.18-rc3

A small collection of FireWire fixes. This includes collections to sparse
and API documentation.

----------------------------------------------------------------
Nirbhay Sharma (1):
      firewire: init_ohci1394_dma: add missing function parameter documentation

Takashi Sakamoto (1):
      firewire: core: fix __must_hold() annotation

 drivers/firewire/core-transaction.c  |  2 +-
 drivers/firewire/init_ohci1394_dma.c | 10 ++++++++++
 2 files changed, 11 insertions(+), 1 deletion(-)


Regards

Takashi Sakamoto

             reply	other threads:[~2025-10-25 10:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-25 10:41 Takashi Sakamoto [this message]
2025-10-25 18:12 ` [GIT PULL] firewire fixes for v6.18-rc3 pr-tracker-bot

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