All of lore.kernel.org
 help / color / mirror / Atom feed
From: Collin Walling <walling@linux.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: thuth@redhat.com, david@redhat.com, qemu-devel@nongnu.org,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	qemu-s390x@nongnu.org, mimu@linux.ibm.com
Subject: Re: [Qemu-devel] [qemu-s390x] [PATCH v1] s390: guest support for diagnose 318 and limit max VCPUs to 247
Date: Wed, 5 Dec 2018 10:27:28 -0500	[thread overview]
Message-ID: <dd18eebb-93be-2b08-0f0e-4a00c19ea388@linux.ibm.com> (raw)
In-Reply-To: <20181205162221.5f537ce7.cohuck@redhat.com>

On 12/5/18 10:22 AM, Cornelia Huck wrote:
> On Wed, 5 Dec 2018 09:59:54 -0500
> Collin Walling <walling@linux.ibm.com> wrote:
> 
>> On 12/5/18 3:29 AM, Christian Borntraeger wrote:
>>> You should clearly review your email list.....
>>>
>>> Adding the "new" Conny, removing Carsten.
>>>   
>>
>> Thanks for taking care of that. I'll be more careful when using the
>> addresses at the top of the files. 
> 
> scripts/get_maintainer.pl -f <file> is probably more useful to get
> current addresses :)
> 

I'll give it a whirl next time. I appreciate the advice! :)

-- 
Respectfully,
- Collin Walling

      reply	other threads:[~2018-12-05 15:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-04 22:18 [Qemu-devel] [PATCH v1] s390: guest support for diagnose 318 and limit max VCPUs to 247 Collin Walling
2018-12-04 22:26 ` Collin Walling
2018-12-05 11:07   ` Cornelia Huck
2018-12-05 14:52     ` [Qemu-devel] [qemu-s390x] " Collin Walling
2018-12-04 23:50 ` [Qemu-devel] " no-reply
2018-12-05  8:26 ` David Hildenbrand
2018-12-05  8:27   ` Christian Borntraeger
2018-12-05 11:54     ` [Qemu-devel] [qemu-s390x] " Cornelia Huck
2018-12-05 11:57       ` David Hildenbrand
2018-12-05 14:58         ` Collin Walling
2018-12-05  8:29 ` [Qemu-devel] " Christian Borntraeger
2018-12-05 14:59   ` Collin Walling
2018-12-05 15:22     ` Cornelia Huck
2018-12-05 15:27       ` Collin Walling [this message]

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=dd18eebb-93be-2b08-0f0e-4a00c19ea388@linux.ibm.com \
    --to=walling@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=mimu@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=thuth@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 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.