Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: James Smart <james.smart@broadcom.com>
To: Christoph Hellwig <hch@lst.de>,
	Eldad.Zinger@dell.com, Leonid.Ravich@emc.com,
	Elad.Grupi@dell.com, sagi@grimberg.me,
	chaitanya.kulkarni@wdc.com
Cc: linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvmet-fc: add a missing __rcu annotation to nvmet_fc_tgt_assoc.queues
Date: Mon, 8 Feb 2021 15:37:04 -0800	[thread overview]
Message-ID: <d120cf63-3f73-d64d-e338-36f75530c397@broadcom.com> (raw)
In-Reply-To: <20210207162028.2959778-1-hch@lst.de>


[-- Attachment #1.1: Type: text/plain, Size: 1099 bytes --]



On 2/7/2021 8:20 AM, Christoph Hellwig wrote:
> Make sparse happy after the recent conversion to RCU lookups.
>
> Fixes: 4e2f02bf77da ("nvmet-fc: use RCU proctection for assoc_list")
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
>
Reviewed-by: James Smart <james.smart@broadcom.com>

Thanks

-- james



-- 
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.

[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4163 bytes --]

[-- Attachment #2: Type: text/plain, Size: 158 bytes --]

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  parent reply	other threads:[~2021-02-08 23:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-07 16:20 [PATCH] nvmet-fc: add a missing __rcu annotation to nvmet_fc_tgt_assoc.queues Christoph Hellwig
2021-02-07 18:58 ` Chaitanya Kulkarni
2021-02-08 23:37 ` James Smart [this message]
2021-02-08 23:44 ` Sagi Grimberg

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=d120cf63-3f73-d64d-e338-36f75530c397@broadcom.com \
    --to=james.smart@broadcom.com \
    --cc=Elad.Grupi@dell.com \
    --cc=Eldad.Zinger@dell.com \
    --cc=Leonid.Ravich@emc.com \
    --cc=chaitanya.kulkarni@wdc.com \
    --cc=hch@lst.de \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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