From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvmet-rdma: Fix missing dma sync to nvme data structures
Date: Mon, 16 Jan 2017 18:30:02 +0100 [thread overview]
Message-ID: <20170116173002.GA6298@lst.de> (raw)
In-Reply-To: <VI1PR0502MB3008EBE381C87D629A784279D17D0@VI1PR0502MB3008.eurprd05.prod.outlook.com>
On Mon, Jan 16, 2017@05:18:15PM +0000, Parav Pandit wrote:
> I see. I will change it to check for the non-zero length instead of non-zero address.
Yes, that should work as well.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: Parav Pandit <parav-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>,
"sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org"
<sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>,
"linux-nvme-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-nvme-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org"
<dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] nvmet-rdma: Fix missing dma sync to nvme data structures
Date: Mon, 16 Jan 2017 18:30:02 +0100 [thread overview]
Message-ID: <20170116173002.GA6298@lst.de> (raw)
In-Reply-To: <VI1PR0502MB3008EBE381C87D629A784279D17D0-o1MPJYiShExKsLr+rGaxW8DSnupUy6xnnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
On Mon, Jan 16, 2017 at 05:18:15PM +0000, Parav Pandit wrote:
> I see. I will change it to check for the non-zero length instead of non-zero address.
Yes, that should work as well.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-01-16 17:30 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-14 16:45 [PATCH] nvmet-rdma: Fix missing dma sync to nvme data structures Parav Pandit
2017-01-14 16:45 ` Parav Pandit
2017-01-14 21:07 ` Sagi Grimberg
2017-01-14 21:07 ` Sagi Grimberg
2017-01-16 15:31 ` Christoph Hellwig
2017-01-16 15:31 ` Christoph Hellwig
2017-01-16 17:18 ` Parav Pandit
2017-01-16 17:18 ` Parav Pandit
2017-01-16 17:30 ` Christoph Hellwig [this message]
2017-01-16 17:30 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2017-01-12 22:45 Parav Pandit
2017-01-12 22:45 ` Parav Pandit
2017-01-13 7:44 ` Christoph Hellwig
2017-01-13 7:44 ` Christoph Hellwig
2017-01-13 15:08 ` Parav Pandit
2017-01-13 15:08 ` Parav Pandit
2017-01-13 19:42 ` Sagi Grimberg
2017-01-13 19:42 ` Sagi Grimberg
2017-01-13 19:50 ` Parav Pandit
2017-01-13 19:50 ` Parav Pandit
2017-01-13 20:01 ` Sagi Grimberg
2017-01-13 20:01 ` Sagi Grimberg
2017-01-14 16:12 ` Parav Pandit
2017-01-14 16:12 ` Parav Pandit
2017-01-14 21:00 ` Sagi Grimberg
2017-01-14 21:00 ` Sagi Grimberg
2017-01-14 16:18 ` Christoph Hellwig
2017-01-14 16:18 ` Christoph Hellwig
2017-01-14 21:04 ` Sagi Grimberg
2017-01-14 21:04 ` Sagi Grimberg
2017-01-13 19:35 ` Sagi Grimberg
2017-01-13 19:35 ` Sagi Grimberg
2017-01-12 22:42 Parav Pandit
2017-01-12 22:42 ` Parav Pandit
2017-01-12 22:45 ` Parav Pandit
2017-01-12 22:45 ` Parav Pandit
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=20170116173002.GA6298@lst.de \
--to=hch@lst.de \
/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.