All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre Morel <pmorel@linux.ibm.com>
To: linux-s390@vger.kernel.org
Subject: Re: [PATCH 1/5] vfio: ccw: Merge BUSY and BOXED states
Date: Tue, 27 Nov 2018 09:07:01 +0000	[thread overview]
Message-ID: <826ab960-e2eb-7e2c-e6d6-7a67c7f878ae@linux.ibm.com> (raw)
In-Reply-To: <497c99a6-4c06-ea3f-d766-6674afa461f1@linux.ibm.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 870 bytes --]

On 26/11/2018 15:53, Eric Farman wrote:
> 
> 
> On 11/19/2018 06:30 AM, Cornelia Huck wrote:
>> On Wed, 17 Oct 2018 11:18:39 +0200
>> Pierre Morel <pmorel@linux.ibm.com> wrote:
>>
>> FWIW, I've created a new vfio-ccw-staging branch where I plan to
>> collect patches prior to putting together a pull request. (I assume I'm
>> still the only vfio-ccw maintainer with a kernel.org account, right?)
> 
> So far as I know.� I can ask around here and see if that should change.
> 
>> The idea is that this branch can collect patches that are fine but are
>> targeted to a later release (fixes would still go via the normal
>> vfio-ccw branch.) Let me know whether that sounds reasonable.
> 
> This sounds fine to me.� Thank you!
> 
>  �- Eric
> 

Forgot to answer but already using your branch.

Thanks,
Pierre

-- 
Pierre Morel
Linux/KVM/QEMU in B�blingen - Germany

       reply	other threads:[~2018-11-27  9:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <497c99a6-4c06-ea3f-d766-6674afa461f1@linux.ibm.com>
2018-11-27  9:07 ` Pierre Morel [this message]
     [not found] <e6eb7332-1d0c-09bf-c599-aa4af38845fc@linux.ibm.com>
2018-10-18  7:42 ` [PATCH 1/5] vfio: ccw: Merge BUSY and BOXED states Pierre Morel

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=826ab960-e2eb-7e2c-e6d6-7a67c7f878ae@linux.ibm.com \
    --to=pmorel@linux.ibm.com \
    --cc=linux-s390@vger.kernel.org \
    /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.