From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: linux-sound@vger.kernel.org
Cc: alsa-devel@alsa-project.org, tiwai@suse.de, broonie@kernel.org
Subject: Re: [PATCH 0/9] ALSA/ASoC: Intel: clarify Copyright information
Date: Thu, 9 May 2024 11:00:06 -0500 [thread overview]
Message-ID: <5630c56e-6639-47f6-81a9-6b52f8b540de@linux.intel.com> (raw)
In-Reply-To: <20240503140359.259762-1-pierre-louis.bossart@linux.intel.com>
On 5/3/24 09:03, Pierre-Louis Bossart wrote:
> This patchset does not change any functionality. It only clarifies the
> Copyright information in ASoC/HDAudio contributions, where an "All
> rights reserved" notice was mistakenly added in a number of files over
> the years, likely due to copy/paste. The Intel template never included
> this statement.
>
> I chose to group all these patches together, they could be merged with
> either of the ALSA or the ASoC tree.
>
> Pierre-Louis Bossart (9):
> ASoC: SOF: Intel: clarify Copyright information
> ASoC: Intel: boards: clarify Copyright information
> ASoC: Intel: common: clarify Copyright information
> ASoC: codecs: Intel: clarify Copyright information
> ASoC: Intel: catpt: clarify Copyright information
> ASoC: Intel: avs: clarify Copyright information
> ASoC: soc-topology-test: clarify Copyright information
The first 7 patches were merged by Mark
> ALSA: hda: clarify Copyright information
> ALSA/ASoC: include: clarify Copyright information
But these last two weren't. Should I resend them? Or can Takashi pick
them? It's just a minor clarification, this can also wait for the next
cycle.
next prev parent reply other threads:[~2024-05-09 16:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 14:03 [PATCH 0/9] ALSA/ASoC: Intel: clarify Copyright information Pierre-Louis Bossart
2024-05-03 14:03 ` [PATCH 1/9] ASoC: SOF: " Pierre-Louis Bossart
2024-05-03 14:03 ` [PATCH 2/9] ASoC: Intel: boards: " Pierre-Louis Bossart
2024-05-03 14:03 ` [PATCH 3/9] ASoC: Intel: common: " Pierre-Louis Bossart
2024-05-03 14:03 ` [PATCH 4/9] ASoC: codecs: Intel: " Pierre-Louis Bossart
2024-05-03 14:03 ` [PATCH 5/9] ASoC: Intel: catpt: " Pierre-Louis Bossart
2024-05-03 14:03 ` [PATCH 6/9] ASoC: Intel: avs: " Pierre-Louis Bossart
2024-05-03 14:03 ` [PATCH 7/9] ASoC: soc-topology-test: " Pierre-Louis Bossart
2024-05-03 14:03 ` [PATCH 8/9] ALSA: hda: " Pierre-Louis Bossart
2024-05-03 14:03 ` [PATCH 9/9] ALSA/ASoC: include: " Pierre-Louis Bossart
2024-05-07 14:35 ` (subset) [PATCH 0/9] ALSA/ASoC: Intel: " Mark Brown
2024-05-09 16:00 ` Pierre-Louis Bossart [this message]
2024-05-09 18:27 ` Takashi Iwai
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=5630c56e-6639-47f6-81a9-6b52f8b540de@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=tiwai@suse.de \
/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