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 fixes for v6.8-rc3
Date: Thu, 1 Feb 2024 21:19:26 +0900	[thread overview]
Message-ID: <20240201121926.GA87292@workstation.local> (raw)

Hi Linus,

The support for legacy layout of configuratom ROM was merged to
v6.8-rc1, while it appears that it is not enough for some devices,
since they have a specific quirk. This pull request includes some
changes to handle the quirk.

The following changes since commit 41bccc98fb7931d63d03f326a746ac4d429c1dd3:

  Linux 6.8-rc2 (2024-01-28 17:01:12 -0800)

are available in the Git repository at:

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

for you to fetch changes up to 47dc55181dcbee69fc84c902e7fb060213b9b8a5:

  firewire: core: search descriptor leaf just after vendor directory entry in root directory (2024-02-01 20:53:18 +0900)

----------------------------------------------------------------
firewire fixes for 6.8-rc3

FireWire subsystem now supports the legacy layout of configuration ROM,
while it appears that some of DV devices in the early 2000's have the
legacy layout with a quirk. This pull request includes some changes to
handle the quirk.

----------------------------------------------------------------
Takashi Sakamoto (2):
      firewire: core: correct documentation of fw_csr_string() kernel API
      firewire: core: search descriptor leaf just after vendor directory entry in root directory

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


Thanks

Takashi Sakamoto

             reply	other threads:[~2024-02-01 12:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01 12:19 Takashi Sakamoto [this message]
2024-02-01 18:23 ` [GIT PULL] firewire fixes for v6.8-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=20240201121926.GA87292@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