From: Dave Hansen <dave.hansen@intel.com>
To: Bard Liao <yung-chuan.liao@linux.intel.com>,
alsa-devel@alsa-project.org, vkoul@kernel.org
Cc: vinod.koul@linaro.org, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org, srinivas.kandagatla@linaro.org,
rander.wang@linux.intel.com, hui.wang@canonical.com,
pierre-louis.bossart@linux.intel.com, sanyog.r.kale@intel.com,
bard.liao@intel.com
Subject: Re: [PATCH v2 2/3] soundwire: Intel: introduce DMI quirks for HP Spectre x360 Convertible
Date: Mon, 12 Apr 2021 14:37:19 -0700 [thread overview]
Message-ID: <de65866a-bb8f-f5c6-2829-42b561f282f7@intel.com> (raw)
In-Reply-To: <20210302075105.11515-3-yung-chuan.liao@linux.intel.com>
On 3/1/21 11:51 PM, Bard Liao wrote:
> +++ b/drivers/soundwire/dmi-quirks.c
> @@ -0,0 +1,66 @@
> +// SPDX-License-Identifier: (GPL-2.0 OR BSD-3-Clause)
> +// Copyright(c) 2021 Intel Corporation.
It looks like this is already in intel-next, so this may be moot. But,
is there a specific reason this is dual licensed? If so, can you please
include information about the license choice in the cover letter of any
future version?
If there is no specific reason for this contribution to be dual
licensed, please make it GPL-2.0 only.
next prev parent reply other threads:[~2021-04-12 21:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 7:51 [PATCH v2 0/3] soundwire: add DMI quirks for overridind addr Bard Liao
2021-03-02 7:51 ` [PATCH v2 1/3] soundwire: add override addr ops Bard Liao
2021-03-02 7:51 ` [PATCH v2 2/3] soundwire: Intel: introduce DMI quirks for HP Spectre x360 Convertible Bard Liao
2021-04-12 21:37 ` Dave Hansen [this message]
2021-04-14 4:08 ` Vinod Koul
2021-04-14 15:21 ` Pierre-Louis Bossart
2021-03-02 7:51 ` [PATCH v2 3/3] soundwire: Intel: add DMI quirk for Dell SKU 0A3E Bard Liao
2021-03-22 12:03 ` [PATCH v2 0/3] soundwire: add DMI quirks for overridind addr Vinod Koul
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=de65866a-bb8f-f5c6-2829-42b561f282f7@intel.com \
--to=dave.hansen@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hui.wang@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rander.wang@linux.intel.com \
--cc=sanyog.r.kale@intel.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=vinod.koul@linaro.org \
--cc=vkoul@kernel.org \
--cc=yung-chuan.liao@linux.intel.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
all inboxes | Powered by JetHome®