The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] firewire updates for v6.9-rc1
Date: Sat, 16 Mar 2024 17:05:44 +0900	[thread overview]
Message-ID: <20240316080544.GA395657@workstation.local> (raw)

Hi Linus,

Please pull firewire updates for v6.9.

At the previous version we have some work to support legacy devices, while
for the next version we have just a small changes to string processing,
as it closely resembles the subsystem for the old technology.

The following changes since commit e8f897f4afef0031fe618a8e94127a0934896aba:

  Linux 6.8 (2024-03-10 13:38:09 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394.git tags/firewire-updates-6.9

for you to fetch changes up to 04f082d39b99f0b7b4b1cada14280f41d99f1e1f:

  firewire: core: fix build failure due to the caller of fw_csr_string() (2024-03-11 10:38:13 +0900)

----------------------------------------------------------------
firewire updates for 6.9

This update includes small changes about page-aligned buffer for string
processing in device attribute.

----------------------------------------------------------------
Li Zhijian (2):
      firewire: Kill unnecessary buf check in device_attribute.show
      firewire: Convert snprintf/sprintf to sysfs_emit

Takashi Sakamoto (1):
      firewire: core: fix build failure due to the caller of fw_csr_string()

 drivers/firewire/core-device.c | 18 +++++-------------
 1 file changed, 5 insertions(+), 13 deletions(-)


Regards

Takashi Sakamoto

             reply	other threads:[~2024-03-16  8:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-16  8:05 Takashi Sakamoto [this message]
2024-03-16 17:22 ` [GIT PULL] firewire updates for v6.9-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=20240316080544.GA395657@workstation.local \
    --to=o-takashi@sakamocchi.jp \
    --cc=linux-kernel@vger.kernel.org \
    --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