From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Piotr Kwapulinski <piotr.kwapulinski@intel.com>,
<intel-wired-lan@lists.osuosl.org>,
Jesse Brandeburg <jesse.brandeburg@intel.com>
Cc: vinicius.gomes@intel.com, netdev@vger.kernel.org,
Jedrzej Jagielski <jedrzej.jagielski@intel.com>,
Stefan Wegrzyn <stefan.wegrzyn@intel.com>,
horms@kernel.org,
Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v2 1/5] ixgbe: Add support for E610 FW Admin Command Interface
Date: Wed, 17 Apr 2024 17:07:37 -0700 [thread overview]
Message-ID: <2378caa5-9b1b-ca89-ca74-e9da91774e87@intel.com> (raw)
In-Reply-To: <20240415103435.6674-2-piotr.kwapulinski@intel.com>
On 4/15/2024 3:34 AM, Piotr Kwapulinski wrote:
...
> +++ b/drivers/net/ethernet/intel/ixgbe/ixgbe_e610.c
> @@ -0,0 +1,492 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/* Copyright(c) 1999 - 2024 Intel Corporation. */
> +
+Jesse
I believe the copyright on new files should be year of the file, not
backdated to the driver's date?
Thanks,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Piotr Kwapulinski <piotr.kwapulinski@intel.com>,
<intel-wired-lan@lists.osuosl.org>,
Jesse Brandeburg <jesse.brandeburg@intel.com>
Cc: <vinicius.gomes@intel.com>, <netdev@vger.kernel.org>,
Jedrzej Jagielski <jedrzej.jagielski@intel.com>,
Stefan Wegrzyn <stefan.wegrzyn@intel.com>, <horms@kernel.org>,
Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v2 1/5] ixgbe: Add support for E610 FW Admin Command Interface
Date: Wed, 17 Apr 2024 17:07:37 -0700 [thread overview]
Message-ID: <2378caa5-9b1b-ca89-ca74-e9da91774e87@intel.com> (raw)
In-Reply-To: <20240415103435.6674-2-piotr.kwapulinski@intel.com>
On 4/15/2024 3:34 AM, Piotr Kwapulinski wrote:
...
> +++ b/drivers/net/ethernet/intel/ixgbe/ixgbe_e610.c
> @@ -0,0 +1,492 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/* Copyright(c) 1999 - 2024 Intel Corporation. */
> +
+Jesse
I believe the copyright on new files should be year of the file, not
backdated to the driver's date?
Thanks,
Tony
next prev parent reply other threads:[~2024-04-18 0:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 10:34 [Intel-wired-lan] [PATCH iwl-next v2 0/5] ixgbe: Add support for Intel(R) E610 device Piotr Kwapulinski
2024-04-15 10:34 ` Piotr Kwapulinski
2024-04-15 10:34 ` [Intel-wired-lan] [PATCH iwl-next v2 1/5] ixgbe: Add support for E610 FW Admin Command Interface Piotr Kwapulinski
2024-04-15 10:34 ` Piotr Kwapulinski
2024-04-18 0:07 ` Tony Nguyen [this message]
2024-04-18 0:07 ` [Intel-wired-lan] " Tony Nguyen
2024-04-15 10:34 ` [Intel-wired-lan] [PATCH iwl-next v2 2/5] ixgbe: Add support for E610 device capabilities detection Piotr Kwapulinski
2024-04-15 10:34 ` Piotr Kwapulinski
2024-04-20 18:18 ` [Intel-wired-lan] " Simon Horman
2024-04-20 18:18 ` Simon Horman
2024-04-22 10:41 ` [Intel-wired-lan] " Kwapulinski, Piotr
2024-04-22 10:41 ` Kwapulinski, Piotr
2024-04-22 18:32 ` [Intel-wired-lan] " Simon Horman
2024-04-22 18:32 ` Simon Horman
2024-04-24 8:13 ` [Intel-wired-lan] " Kwapulinski, Piotr
2024-04-24 8:13 ` Kwapulinski, Piotr
2024-04-24 8:49 ` [Intel-wired-lan] " Kwapulinski, Piotr
2024-04-24 8:49 ` Kwapulinski, Piotr
2024-04-15 10:34 ` [Intel-wired-lan] [PATCH iwl-next v2 3/5] ixgbe: Add link management support for E610 device Piotr Kwapulinski
2024-04-15 10:34 ` Piotr Kwapulinski
2024-04-15 10:34 ` [Intel-wired-lan] [PATCH iwl-next v2 4/5] ixgbe: Add support for NVM handling in " Piotr Kwapulinski
2024-04-15 10:34 ` Piotr Kwapulinski
2024-04-15 10:34 ` [Intel-wired-lan] [PATCH iwl-next v2 5/5] ixgbe: Enable link management " Piotr Kwapulinski
2024-04-15 10:34 ` Piotr Kwapulinski
2024-04-18 0:07 ` [Intel-wired-lan] " Tony Nguyen
2024-04-18 0:07 ` Tony Nguyen
2024-04-16 5:17 ` [Intel-wired-lan] [PATCH iwl-next v2 0/5] ixgbe: Add support for Intel(R) " Kwapulinski, Piotr
2024-04-16 5:17 ` Kwapulinski, Piotr
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=2378caa5-9b1b-ca89-ca74-e9da91774e87@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jedrzej.jagielski@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=piotr.kwapulinski@intel.com \
--cc=stefan.wegrzyn@intel.com \
--cc=vinicius.gomes@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.