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 updates for v6.13-rc1
Date: Sat, 23 Nov 2024 16:13:06 +0900 [thread overview]
Message-ID: <20241123071306.GA108525@workstation.local> (raw)
Hi Linus,
Please pull some updates for 6.13 from FireWire subsystem. The
development activity has been relatively quiet, so only a few
commits are included in this PR.
The following changes since commit 9852d85ec9d492ebef56dc5f229416c925758edc:
Linux 6.12-rc1 (2024-09-29 15:06:19 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394.git tags/firewire-updates-6.13
for you to fetch changes up to 4752e8cde8344cb8673abdefe0dd74e9a2fe23ad:
tools/firewire: Fix several incorrect format specifiers (2024-11-14 09:12:04 +0900)
----------------------------------------------------------------
firewire updates for v6.13
A few updates for the 6.13 kernel, including some typo corrections in the
software stack and some fixes for tools. Additionally, it includes a
change resulting from the deprecation of a kernel API in the PCI
subsystem.
----------------------------------------------------------------
Luo Yifan (1):
tools/firewire: Fix several incorrect format specifiers
Philipp Stanner (1):
firewire: ohci: Replace deprecated PCI functions
Shen Lichuan (1):
firewire: Correct some typos
drivers/firewire/core-topology.c | 2 +-
drivers/firewire/core.h | 2 +-
drivers/firewire/ohci.c | 11 +++++------
tools/firewire/decode-fcp.c | 2 +-
tools/firewire/nosy-dump.c | 6 +++---
5 files changed, 11 insertions(+), 12 deletions(-)
Regards
Takashi Sakamoto
next reply other threads:[~2024-11-23 7:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-23 7:13 Takashi Sakamoto [this message]
2024-11-26 1:41 ` [GIT PULL] firewire updates for v6.13-rc1 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=20241123071306.GA108525@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