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
Subject: [GIT PULL] firewire updates for 6.8
Date: Wed, 10 Jan 2024 20:13:31 +0900	[thread overview]
Message-ID: <20240110111331.GA138108@workstation.local> (raw)

Hi Linus,

The following changes since commit 0dd3ee31125508cd67f7e7172247f05b7fd1753a:

  Linux 6.7 (2024-01-07 12:18:38 -0800)

are available in the Git repository at:

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

for you to fetch changes up to 986c20bb3e67d0171c0c2e4acd25429b1876b963:

  firewire: core: fill model field in modalias of unit device for legacy layout of configuration ROM (2024-01-10 18:37:13 +0900)

----------------------------------------------------------------
firewire updates for 6.8

This update includes the series of changes related to device attributes,
as well as slight code refactoring.

Some old devices are recognized to have legacy layout of configuration ROM.
They have an inconvenience that FireWire subsystem adds no attributes for
vendor information to corresponding devices. The main purpose of this
update is to rectify the inconvenience.

We have a slight concern about regression. The update changes the value of
modalias for the unit devices by populating its model field, which was
previously left as zero in the case. I've assessed the potential impact of
this change and anticipate it to have minimal concern for both the kernel
and user lands. The change is enough acceptable.

----------------------------------------------------------------
Greg Kroah-Hartman (1):
      firewire: make fw_bus_type const

Takashi Sakamoto (8):
      firewire: core: adds constant qualifier for local helper functions
      firewire: core: replace magic number with macro
      firewire: test: add KUnit test for device attributes
      firewire: test: add test of device attributes for simple AV/C device
      firewire: test: add test of device attributes for legacy AV/C device
      firewire: core: detect numeric model identifier for legacy layout of configuration ROM
      firewire: core: detect model name for legacy layout of configuration ROM
      firewire: core: fill model field in modalias of unit device for legacy layout of configuration ROM

 drivers/firewire/.kunitconfig            |   1 +
 drivers/firewire/Kconfig                 |  16 +++++++++++++
 drivers/firewire/core-device.c           | 129 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++----------------------
 drivers/firewire/device-attribute-test.c | 251 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 include/linux/firewire.h                 |   2 +-
 5 files changed, 370 insertions(+), 29 deletions(-)
 create mode 100644 drivers/firewire/device-attribute-test.c


Regards

Takashi Sakamoto

             reply	other threads:[~2024-01-10 11:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-10 11:13 Takashi Sakamoto [this message]
2024-01-12 22:20 ` [GIT PULL] firewire updates for 6.8 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=20240110111331.GA138108@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