All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dongwon Kim <dongwon.kim@intel.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Markus Armbruster" <armbru@redhat.com>,
	qemu-devel@nongnu.org,
	"Daniel P . Berrangé" <berrange@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Vivek Kasireddy" <vivek.kasireddy@intel.com>
Subject: Re: [PATCH v3 2/2] ui/gtk: a new array param monitor to specify the target displays
Date: Tue, 5 Jul 2022 14:03:02 -0700	[thread overview]
Message-ID: <20220705210302.GA582@dongwonk-MOBL.amr.corp.intel.com> (raw)
In-Reply-To: <20220701095848.sqoxzeplraft7hzc@sirius.home.kraxel.org>

Thanks, yeah, I will remove '-' and resubmitt the patch.

On Fri, Jul 01, 2022 at 11:58:48AM +0200, Gerd Hoffmann wrote:
>   Hi,
> 
> > > +# @monitor:     Array of numbers, each of which represents physical
> > > +#               monitor where GTK window containing a given VC will be
> > > +#               placed. Each monitor number in the array will be
> > > +#               associated with a virtual-console starting from VC0.
> > 
> > Drop the hyphen in "virtual-console".
> > 
> > Is the term "virtual console" obvious?  Gerd?
> 
> I think so, same term is used elsewhere too for the same concept.
> 
> take care,
>   Gerd
> 


  reply	other threads:[~2022-07-05 21:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30  0:51 [PATCH v3 0/2] handling guest multiple displays Dongwon Kim
2022-06-30  0:51 ` [PATCH v3 1/3] ui/gtk: detach VCs for additional guest displays Dongwon Kim
2022-06-30 15:04   ` Markus Armbruster
2022-06-30  0:51 ` [PATCH v3 2/2] ui/gtk: a new array param monitor to specify the target displays Dongwon Kim
2022-06-30 15:19   ` Markus Armbruster
2022-07-01  9:58     ` Gerd Hoffmann
2022-07-05 21:03       ` Dongwon Kim [this message]
2022-07-05 21:06     ` Dongwon Kim
2022-07-06  4:21       ` Markus Armbruster

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=20220705210302.GA582@dongwonk-MOBL.amr.corp.intel.com \
    --to=dongwon.kim@intel.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=vivek.kasireddy@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 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.