From: hch@lst.de (Christoph Hellwig)
Subject: [PATCHv3] nvmet-rdma: Fix missing dma sync to nvme data structures
Date: Thu, 19 Jan 2017 16:46:01 +0100 [thread overview]
Message-ID: <20170119154601.GA597@lst.de> (raw)
In-Reply-To: <VI1PR0502MB300864C57897C37D4397A76AD17E0@VI1PR0502MB3008.eurprd05.prod.outlook.com>
On Thu, Jan 19, 2017@03:45:30PM +0000, Parav Pandit wrote:
> I agree. I should have taken care of that.
> Shall I resend patch with same indentation at all places or this can be taken care during commit?
I think Sagi or I can just take care of it on commit.
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: [PATCHv3] nvmet-rdma: Fix missing dma sync to nvme data structures
Date: Thu, 19 Jan 2017 16:46:01 +0100 [thread overview]
Message-ID: <20170119154601.GA597@lst.de> (raw)
In-Reply-To: <VI1PR0502MB300864C57897C37D4397A76AD17E0-o1MPJYiShExKsLr+rGaxW8DSnupUy6xnnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
On Thu, Jan 19, 2017 at 03:45:30PM +0000, Parav Pandit wrote:
> I agree. I should have taken care of that.
> Shall I resend patch with same indentation at all places or this can be taken care during commit?
I think Sagi or I can just take care of it on commit.
--
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-19 15:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 0:22 [PATCHv3] nvmet-rdma: Fix missing dma sync to nvme data structures Parav Pandit
2017-01-19 0:22 ` Parav Pandit
2017-01-19 7:42 ` Sagi Grimberg
2017-01-19 7:42 ` Sagi Grimberg
2017-01-19 15:22 ` Christoph Hellwig
2017-01-19 15:22 ` Christoph Hellwig
2017-01-19 15:45 ` Parav Pandit
2017-01-19 15:45 ` Parav Pandit
2017-01-19 15:46 ` Christoph Hellwig [this message]
2017-01-19 15:46 ` Christoph Hellwig
2017-01-19 15:51 ` Parav Pandit
2017-01-19 15:51 ` 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=20170119154601.GA597@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.