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.6
Date: Sat, 9 Sep 2023 12:34:57 +0900 [thread overview]
Message-ID: <20230909033457.GA59845@workstation.local> (raw)
Hi Linus,
Please pull firewire updates for v6.6.
The following changes since commit 2dde18cd1d8fac735875f2e4987f11817cc0bc2c:
Linux 6.5 (2023-08-27 14:49:51 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394.git tags/firewire-updates-6.6
for you to fetch changes up to fd416616d0995f4947dd0a7a8c2ac4d9f916a9d0:
firewire: allow deactivating the IEEE1394 menuconfig section at once (2023-09-07 19:11:17 +0900)
----------------------------------------------------------------
firewire updates for 6.6
The pull request includes a slight change of configuration entry in Kconfig.
In the second half of 6.6 merge window, Jan Engelhardt sent the change. It
allows any front ends of Kconfig to deactivate FireWire subsystem at a
clip. I would usually nack such late change and postpone it next merge
window, while it includes no impact to existent CI build in the world since
it just a hint for the front ends. I would like to include the change in
the time as an exception.
----------------------------------------------------------------
Jan Engelhardt (1):
firewire: allow deactivating the IEEE1394 menuconfig section at once
drivers/firewire/Kconfig | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
next reply other threads:[~2023-09-09 3:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-09 3:34 Takashi Sakamoto [this message]
2023-09-09 18:28 ` [GIT PULL] firewire updates for 6.6 Linus Torvalds
2023-09-10 2:20 ` Takashi Sakamoto
2023-09-09 22:11 ` [PATCH] firewire: dissolve one menu indirection Jan Engelhardt
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=20230909033457.GA59845@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