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.10-rc1
Date: Sun, 2 Jun 2024 08:43:50 +0900 [thread overview]
Message-ID: <20240601234350.GA424664@workstation.local> (raw)
Hi Linus,
Please apply a single trivial patch from FireWire subsystem to your tree.
The following changes since commit 1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0:
Linux 6.10-rc1 (2024-05-26 15:20:12 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394.git tags/firewire-fixes-6.10-rc1
for you to fetch changes up to f94b77709e82242c1101e59a90a7807455c4ab2a:
firewire: add missing MODULE_DESCRIPTION() to test modules (2024-05-27 07:34:58 +0900)
----------------------------------------------------------------
firewire fixes for 6.10-rc1
After merging a commit 1fffe7a34c89 ("script: modpost: emit a warning when
the description is missing"), MODULE_DESCRIPTOR seems to be mandatory for
kernel modules. In FireWire subsystem, the most of practical kernel modules
have the field, while KUnit test modules do not. A single patch is applied
to fix them.
----------------------------------------------------------------
Jeff Johnson (1):
firewire: add missing MODULE_DESCRIPTION() to test modules
drivers/firewire/packet-serdes-test.c | 1 +
drivers/firewire/uapi-test.c | 1 +
2 files changed, 2 insertions(+)
Regards
Takashi Sakamoto
next reply other threads:[~2024-06-01 23:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-01 23:43 Takashi Sakamoto [this message]
2024-06-02 0:44 ` 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=20240601234350.GA424664@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
all inboxes | Powered by JetHome®