From: Christoph Hellwig <hch@lst.de>
To: leonid.ravich@dell.com
Cc: Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>,
james.smart@broadcom.com, linux-nvme@lists.infradead.org,
linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
lravich@gmail.com
Subject: Re: [PATCH v2] nvmet-fc: associations list protected by rcu, instead of spinlock_irq where possible.
Date: Tue, 12 Jan 2021 09:26:41 +0100 [thread overview]
Message-ID: <20210112082641.GA25502@lst.de> (raw)
In-Reply-To: <1609697575-103348-2-git-send-email-leonid.ravich@dell.com>
Thanks,
applied to nvme-5.11.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: leonid.ravich@dell.com
Cc: james.smart@broadcom.com, lravich@gmail.com,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] nvmet-fc: associations list protected by rcu, instead of spinlock_irq where possible.
Date: Tue, 12 Jan 2021 09:26:41 +0100 [thread overview]
Message-ID: <20210112082641.GA25502@lst.de> (raw)
In-Reply-To: <1609697575-103348-2-git-send-email-leonid.ravich@dell.com>
Thanks,
applied to nvme-5.11.
next prev parent reply other threads:[~2021-01-12 8:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-24 11:05 [PATCH] nvmet-fc: associations list replaced with hlist rcu, leonid.ravich
2020-12-24 11:05 ` leonid.ravich
2020-12-24 11:05 ` leonid.ravich
2020-12-24 11:05 ` leonid.ravich
2021-01-11 18:12 ` James Smart
2021-01-11 18:12 ` James Smart
2020-12-25 21:09 ` kernel test robot
2020-12-25 21:09 ` kernel test robot
2020-12-25 21:09 ` kernel test robot
2021-01-03 18:12 ` [PATCH v2] nvmet-fc: associations list protected by rcu, instead of spinlock_irq where possible leonid.ravich
2021-01-03 18:12 ` leonid.ravich
2021-01-03 18:12 ` leonid.ravich
2021-01-03 18:12 ` leonid.ravich
2021-01-11 23:46 ` James Smart
2021-01-11 23:46 ` James Smart
2021-01-12 8:26 ` Christoph Hellwig [this message]
2021-01-12 8:26 ` Christoph Hellwig
2021-01-11 8:11 ` Christoph Hellwig
2021-01-11 8:11 ` Christoph Hellwig
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=20210112082641.GA25502@lst.de \
--to=hch@lst.de \
--cc=chaitanya.kulkarni@wdc.com \
--cc=james.smart@broadcom.com \
--cc=leonid.ravich@dell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=lravich@gmail.com \
--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 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.