From: Krzysztof Kozlowski <krzk@kernel.org>
To: Justin Tee <justintee8345@gmail.com>, linux-scsi@vger.kernel.org
Cc: jsmart2021@gmail.com, justin.tee@broadcom.com
Subject: Re: [PATCH 11/11] lpfc: Copyright updates for 14.4.0.12 patches
Date: Tue, 28 Oct 2025 08:32:27 +0100 [thread overview]
Message-ID: <0e8f0242-6bc2-4202-bc6f-4aeb0d150e21@kernel.org> (raw)
In-Reply-To: <20251027235446.77200-12-justintee8345@gmail.com>
On 28/10/2025 00:54, Justin Tee wrote:
> Update copyrights to 2025 for files modified in the 14.4.0.12 patch set.
This makes no sense on its own. We do not care about copyrights and such
patch has zero meaning to us. Plus it should be result of copyright
work, IOW, must be squashed if at all.
>
> Signed-off-by: Justin Tee <justin.tee@broadcom.com>
Does not match from address.
> ---
> drivers/scsi/lpfc/lpfc_disc.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/scsi/lpfc/lpfc_disc.h b/drivers/scsi/lpfc/lpfc_disc.h
> index 511aae481b77..51cb8571c049 100644
> --- a/drivers/scsi/lpfc/lpfc_disc.h
> +++ b/drivers/scsi/lpfc/lpfc_disc.h
> @@ -1,7 +1,7 @@
> /*******************************************************************
> * This file is part of the Emulex Linux Device Driver for *
> * Fibre Channel Host Bus Adapters. *
> - * Copyright (C) 2017-2024 Broadcom. All Rights Reserved. The term *
> + * Copyright (C) 2017-2025 Broadcom. All Rights Reserved. The term *
> * “Broadcom” refers to Broadcom Inc. and/or its subsidiaries. *
> * Copyright (C) 2004-2013 Emulex. All rights reserved. *
> * EMULEX and SLI are trademarks of Emulex. *
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-10-28 7:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 23:54 [PATCH 00/11] Update lpfc to revision 14.4.0.12 Justin Tee
2025-10-27 23:54 ` [PATCH 01/11] lpfc: Update various NPIV diagnostic log messaging Justin Tee
2025-10-27 23:54 ` [PATCH 02/11] lpfc: Revise discovery related function headers and comments Justin Tee
2025-10-27 23:54 ` [PATCH 03/11] lpfc: Remove redundant NULL ptr assignment in lpfc_els_free_iocb Justin Tee
2025-10-27 23:54 ` [PATCH 04/11] lpfc: Ensure unregistration of rpis for received PLOGIs Justin Tee
2025-10-27 23:54 ` [PATCH 05/11] lpfc: Fix leaked ndlp krefs when in point-to-point topology Justin Tee
2025-10-27 23:54 ` [PATCH 06/11] lpfc: Modify kref handling for Fabric Controller ndlps Justin Tee
2025-10-27 23:54 ` [PATCH 07/11] lpfc: Fix reusing an ndlp that is marked NLP_DROPPED during FLOGI Justin Tee
2025-10-27 23:54 ` [PATCH 08/11] lpfc: Allow support for BB credit recovery in point-to-point topology Justin Tee
2025-10-27 23:54 ` [PATCH 09/11] lpfc: Add capability to register Platform Name ID to fabric Justin Tee
2025-10-28 7:34 ` Krzysztof Kozlowski
2025-10-28 23:16 ` Justin Tee
2025-10-29 5:20 ` Krzysztof Kozlowski
2025-10-29 18:14 ` Justin Tee
2025-10-30 5:29 ` Krzysztof Kozlowski
2025-10-30 17:34 ` Justin Tee
2025-10-27 23:54 ` [PATCH 10/11] lpfc: Update lpfc version to 14.4.0.12 Justin Tee
2025-10-28 7:33 ` Krzysztof Kozlowski
2025-10-28 23:13 ` Justin Tee
2025-10-27 23:54 ` [PATCH 11/11] lpfc: Copyright updates for 14.4.0.12 patches Justin Tee
2025-10-28 7:32 ` Krzysztof Kozlowski [this message]
2025-10-28 23:13 ` Justin Tee
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=0e8f0242-6bc2-4202-bc6f-4aeb0d150e21@kernel.org \
--to=krzk@kernel.org \
--cc=jsmart2021@gmail.com \
--cc=justin.tee@broadcom.com \
--cc=justintee8345@gmail.com \
--cc=linux-scsi@vger.kernel.org \
/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