linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Miklos Szeredi <mszeredi@redhat.com>,
	Vivek Goyal <vgoyal@redhat.com>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] virtio-fs: rename num_queues to num_request_queues
Date: Wed, 25 Sep 2019 10:23:36 -0400	[thread overview]
Message-ID: <20190925102255-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAJfpeguDfn=3fnYoAj78H7fEvZ1bSt0dtEQ9J1Gk3mJDVA-YxQ@mail.gmail.com>

On Wed, Sep 18, 2019 at 08:22:06PM +0200, Miklos Szeredi wrote:
> On Wed, Sep 18, 2019 at 6:48 PM Dr. David Alan Gilbert
> <dgilbert@redhat.com> wrote:
> >
> > * Stefan Hajnoczi (stefanha@redhat.com) wrote:
> > > The final version of the virtio-fs device specification renamed the
> > > num_queues field to num_request_queues.  The semantics are unchanged but
> > > this name is clearer.
> > >
> > > Use the new name in the code.
> > >
> > > Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> >
> > Consistent with the latest version that's just passed the voting;
> > (see
> > https://lists.oasis-open.org/archives/virtio-dev/201908/msg00113.html )
> > so:
> >
> >
> > Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> >
> > > ---
> > > Feel free to squash this patch.
> 
> Thanks, folded this one as well.
> 
> Miklos

So what's the plan for merging all this?
Doesn't look like it was sent in the merge window, nor is
it in linux-next.

-- 
MST

  reply	other threads:[~2019-09-25 14:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-17 11:44 [PATCH] virtio-fs: rename num_queues to num_request_queues Stefan Hajnoczi
2019-09-18 16:48 ` Dr. David Alan Gilbert
2019-09-18 18:22   ` Miklos Szeredi
2019-09-25 14:23     ` Michael S. Tsirkin [this message]
2019-09-25 14:31       ` Miklos Szeredi
2019-09-30  9:48       ` Dr. David Alan Gilbert

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=20190925102255-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=mszeredi@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=vgoyal@redhat.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).