From: Jonathan Cameron <jic23@kernel.org>
To: Trevor Gamblin <tgamblin@baylibre.com>
Cc: "Michael Hennerich" <Michael.Hennerich@analog.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: adc: ad7625: drop BSD license tag
Date: Sat, 18 Jan 2025 15:55:10 +0000 [thread overview]
Message-ID: <20250118155510.7532d5c5@jic23-huawei> (raw)
In-Reply-To: <20250114-ad7625_license-v1-1-6555b7be05ab@baylibre.com>
On Tue, 14 Jan 2025 12:31:55 -0500
Trevor Gamblin <tgamblin@baylibre.com> wrote:
> The ad7625 driver was submitted under a dual BSD/GPL license, but this
> isn't a requirement for the code, and adds extra complexity. To make it
> consistent with similar drivers, drop the BSD tag and leave it as
> GPL-2.0-only.
>
> Suggested-by: Nuno Sa <nuno.sa@analog.com>
> Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com>
Your code, so your choice either way. Applied.
> ---
> drivers/iio/adc/ad7625.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/adc/ad7625.c b/drivers/iio/adc/ad7625.c
> index aefe3bf75c91..8b020f22c5a8 100644
> --- a/drivers/iio/adc/ad7625.c
> +++ b/drivers/iio/adc/ad7625.c
> @@ -1,4 +1,4 @@
> -// SPDX-License-Identifier: (GPL-2.0-only OR BSD-3-Clause)
> +// SPDX-License-Identifier: (GPL-2.0-only)
> /*
> * Analog Devices Inc. AD7625 ADC driver
> *
> @@ -680,5 +680,5 @@ module_platform_driver(ad7625_driver);
>
> MODULE_AUTHOR("Trevor Gamblin <tgamblin@baylibre.com>");
> MODULE_DESCRIPTION("Analog Devices AD7625 ADC");
> -MODULE_LICENSE("Dual BSD/GPL");
> +MODULE_LICENSE("GPL");
> MODULE_IMPORT_NS("IIO_BACKEND");
>
> ---
> base-commit: 5bc55a333a2f7316b58edc7573e8e893f7acb532
> change-id: 20250114-ad7625_license-bcbaaa3bf449
>
> Best regards,
prev parent reply other threads:[~2025-01-18 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 17:31 Trevor Gamblin
2025-01-18 15:55 ` Jonathan Cameron [this message]
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=20250118155510.7532d5c5@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=tgamblin@baylibre.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®