From: kernel test robot <lkp@intel.com>
To: Johannes Berg <johannes.berg@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
dave.hansen@intel.com, dan.j.williams@intel.com,
Luca Coelho <luciano.coelho@intel.com>
Subject: drivers/net/wireless/intel/iwlwifi/fw/notif-wait.c:1:0: warning: dual license is used, are you sure you want to do this.
Date: Fri, 17 Sep 2021 05:31:51 +0800 [thread overview]
Message-ID: <202109170547.aahNWXFL-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: b60cee5bae733f49ba33840804c159a8e474cfda
commit: 8e99ea8d09a159d46069faef10721a3f8436d2fd iwlwifi: use SPDX tags
date: 9 months ago
While copyright holders are free to license their software any
way they see fit, the kernel community prefers GPL-2.0-only or
GPL-2.0-or-later for kernel contributions.
If you are sure you want to submit with a dual license, please
ensure that your commit message calls out the practical reasons
for which you want to do this, including the specific other
projects you expect to make use of this code.
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
dualliccheck warnings: (new ones prefixed by >>)
>> drivers/net/wireless/intel/iwlwifi/fw/notif-wait.c:1:0: warning: dual license is used, are you sure you want to do this.
--
>> drivers/net/wireless/intel/iwlwifi/pcie/tx.c:1:0: warning: dual license is used, are you sure you want to do this.
--
>> drivers/net/wireless/intel/iwlwifi/pcie/ctxt-info.c:1:0: warning: dual license is used, are you sure you want to do this.
vim +1 drivers/net/wireless/intel/iwlwifi/fw/notif-wait.c
> 1 // SPDX-License-Identifier: GPL-2.0 OR BSD-3-Clause
2 /*
3 * Copyright (C) 2005-2014 Intel Corporation
4 * Copyright (C) 2015-2017 Intel Deutschland GmbH
5 */
6 #include <linux/sched.h>
7 #include <linux/export.h>
8
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-09-16 21:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202109170547.aahNWXFL-lkp@intel.com \
--to=lkp@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=johannes.berg@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luciano.coelho@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