From: Tim Bird <tim.bird@sony.com>
To: perex@perex.cz, tiwai@suse.com, clemens@ladisch.de
Cc: linux-spdx@vger.kernel.org, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org, Tim Bird <tim.bird@sony.com>
Subject: [PATCH v2] ALSA: usb-audio: Add SPDX id to midi.c
Date: Tue, 17 Feb 2026 16:41:24 -0700 [thread overview]
Message-ID: <20260217234124.242053-1-tim.bird@sony.com> (raw)
Add an SPDX-License-Identifier line to sound/usb/midi.c
Use 'BSD-Source-Code' as part of the OR for the
license id.
Signed-off-by: Tim Bird <tim.bird@sony.com>
---
This patch depends on the one for opl4 sound driver, as that
one adds the BSD-Source-Code license for the LICENSES directory.
V1 -> V2
- Change to use BSD-Source-Code, from the weird LicenseRef variant
thing I was doing before. This is a supported SPDX ID.
- Use better subject prefix (ALSA: usb-audio:)
---
sound/usb/midi.c | 27 +--------------------------
1 file changed, 1 insertion(+), 26 deletions(-)
diff --git a/sound/usb/midi.c b/sound/usb/midi.c
index dd8249e75970..e6e8618a232a 100644
--- a/sound/usb/midi.c
+++ b/sound/usb/midi.c
@@ -1,3 +1,4 @@
+// SPDX-License-Identifier: GPL-2.0-or-later OR BSD-Source-Code
/*
* usbmidi.c - ALSA USB MIDI driver
*
@@ -7,32 +8,6 @@
* Based on the OSS usb-midi driver by NAGANO Daisuke,
* NetBSD's umidi driver by Takuya SHIOZAKI,
* the "USB Device Class Definition for MIDI Devices" by Roland
- *
- * Redistribution and use in source and binary forms, with or without
- * modification, are permitted provided that the following conditions
- * are met:
- * 1. Redistributions of source code must retain the above copyright
- * notice, this list of conditions, and the following disclaimer,
- * without modification.
- * 2. The name of the author may not be used to endorse or promote products
- * derived from this software without specific prior written permission.
- *
- * Alternatively, this software may be distributed and/or modified under the
- * terms of the GNU General Public License as published by the Free Software
- * Foundation; either version 2 of the License, or (at your option) any later
- * version.
- *
- * THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
- * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
- * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
- * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR
- * ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
- * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
- * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
- * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
- * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
- * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
- * SUCH DAMAGE.
*/
#include <linux/kernel.h>
--
2.43.0
next reply other threads:[~2026-02-17 23:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 23:41 Tim Bird [this message]
2026-02-18 1:14 ` [PATCH v2] ALSA: usb-audio: Add SPDX id to midi.c Richard Fontana
2026-02-18 17:56 ` Bird, Tim
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=20260217234124.242053-1-tim.bird@sony.com \
--to=tim.bird@sony.com \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
/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