From: Stephen Hemminger <stephen@networkplumber.org>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: tiwei.bie@intel.com, zhihong.wang@intel.com,
jfreimann@redhat.com, dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] vhost: flush IOTLB cache on new mem table handling
Date: Thu, 2 Aug 2018 10:09:30 -0700 [thread overview]
Message-ID: <20180802100930.230e0b14@xeon-e3> (raw)
In-Reply-To: <20180802163727.5376-1-maxime.coquelin@redhat.com>
On Thu, 2 Aug 2018 18:37:27 +0200
Maxime Coquelin <maxime.coquelin@redhat.com> wrote:
>
> +void
> +vhost_user_iotlb_flush_all(struct vhost_virtqueue *vq)
> +{
> + vhost_user_iotlb_cache_remove_all(vq);
> + vhost_user_iotlb_pending_remove_all(vq);
> +}
> +
Wrong indentation, you don't want two tabs here, only one.
next prev parent reply other threads:[~2018-08-02 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-02 16:37 [dpdk-stable] " Maxime Coquelin
2018-08-02 17:09 ` Stephen Hemminger [this message]
2018-08-02 17:11 ` [dpdk-stable] [dpdk-dev] " Maxime Coquelin
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=20180802100930.230e0b14@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=jfreimann@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=stable@dpdk.org \
--cc=tiwei.bie@intel.com \
--cc=zhihong.wang@intel.com \
/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).