From: Greg KH <gregkh@linuxfoundation.org>
To: Justin Tee <justintee8345@gmail.com>
Cc: Justin Tee <justin.tee@broadcom.com>,
Bin Lan <bin.lan.cn@windriver.com>,
stable@vger.kernel.org, bass@buaa.edu.cn, islituo@gmail.com,
loberman@redhat.com, martin.petersen@oracle.com
Subject: Re: [PATCH 5.10.y] scsi: lpfc: Fix a possible data race in lpfc_unregister_fcf_rescan()
Date: Sat, 5 Apr 2025 08:34:05 +0100 [thread overview]
Message-ID: <2025040517-ranch-rifling-3e8f@gregkh> (raw)
In-Reply-To: <CABPRKS-WXKmSDyWbEtMHeTbRXctjc5GFwOWJAdzZ+vQHNZBLHw@mail.gmail.com>
On Fri, Apr 04, 2025 at 01:23:49PM -0700, Justin Tee wrote:
> Hi Greg,
>
> > > This electronic communication and the information and any files transmitted
> > > with it, or attached to it, are confidential and are intended solely for
> > > the use of the individual or entity to whom it is addressed and may contain
> > > information that is confidential, legally privileged, protected by privacy
> > > laws, or otherwise restricted from disclosure to anyone else. If you are
> > > not the intended recipient or the person responsible for delivering the
> > > e-mail to the intended recipient, you are hereby notified that any use,
> > > copying, distributing, dissemination, forwarding, printing, or copying of
> > > this e-mail is strictly prohibited. If you received this e-mail in error,
> > > please return the e-mail to the sender, delete it from your computer, and
> > > destroy any printed copy of it.
> >
> > Now deleted.
>
> You and everyone on this mailing list are intended recipients, so
> there is no need to delete.
Not true, you said this is "confidential" and according to our legal
advivice, that is not allowed to be on a change for a contribution to
Linux. Please remove this type of message if you wish to contribute to
open source projects.
thanks,
greg k-h
next prev parent reply other threads:[~2025-04-05 7:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 3:29 [PATCH 5.15.y] scsi: lpfc: Fix a possible data race in lpfc_unregister_fcf_rescan() bin.lan.cn
2025-04-03 3:29 ` [PATCH 5.10.y] " bin.lan.cn
2025-04-03 10:52 ` Bin Lan
2025-04-03 20:58 ` Justin Tee
2025-04-04 6:28 ` Greg KH
2025-04-04 20:23 ` Justin Tee
2025-04-05 7:34 ` Greg KH [this message]
2025-04-03 15:39 ` Sasha Levin
2025-04-03 15:38 ` [PATCH 5.15.y] " Sasha Levin
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=2025040517-ranch-rifling-3e8f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bass@buaa.edu.cn \
--cc=bin.lan.cn@windriver.com \
--cc=islituo@gmail.com \
--cc=justin.tee@broadcom.com \
--cc=justintee8345@gmail.com \
--cc=loberman@redhat.com \
--cc=martin.petersen@oracle.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).