Re: [PATCH 1/5] vfio: ccw: Merge BUSY and BOXED states

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On 11/19/2018 06:30 AM, Cornelia Huck wrote:
On Wed, 17 Oct 2018 11:18:39 +0200
Pierre Morel <pmorel@xxxxxxxxxxxxx> 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


VFIO_CCW_STATE_BOXED and VFIO_CCW_STATE_BUSY have
identical actions for the same events.

Let's merge both into a single state to simplify the code.
We choose to keep VFIO_CCW_STATE_BUSY.

Signed-off-by: Pierre Morel <pmorel@xxxxxxxxxxxxx>
---
  drivers/s390/cio/vfio_ccw_fsm.c     | 7 +------
  drivers/s390/cio/vfio_ccw_private.h | 1 -
  2 files changed, 1 insertion(+), 7 deletions(-)

Thanks, queued to vfio-ccw-staging.





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Kernel Development]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Info]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Linux Media]     [Device Mapper]

  Powered by Linux