On Mon, 8 May 2017 13:29:27 +0800 Dong Jia Shi <bjsdjshi@xxxxxxxxxxxxxxxxxx> wrote: > * Cornelia Huck <cornelia.huck@xxxxxxxxxx> [2017-05-05 14:20:14 +0200]: > > > On Fri, 5 May 2017 04:03:52 +0200 > > Dong Jia Shi <bjsdjshi@xxxxxxxxxxxxxxxxxx> wrote: > > > > > Add Cornelia Huck as the vfio-ccw maintainer. > > > > > > Signed-off-by: Dong Jia Shi <bjsdjshi@xxxxxxxxxxxxxxxxxx> > > > --- > > > MAINTAINERS | 5 +++++ > > > 1 file changed, 5 insertions(+) > > > > > > diff --git a/MAINTAINERS b/MAINTAINERS > > > index cae3b09..c1f9917 100644 > > > --- a/MAINTAINERS > > > +++ b/MAINTAINERS > > > @@ -999,6 +999,11 @@ S: Supported > > > F: hw/vfio/* > > > F: include/hw/vfio/ > > > > > > +vfio-ccw > > > +M: Cornelia Huck <cornelia.huck@xxxxxxxxxx> > > > +S: Supported > > > +F: hw/vfio/ccw.c > > > > The other code related to vfio-ccw is entangled with the other virtual > > css code, so this is probably really the only file that needs to be > > listed separately. > "hw/s390x/" and "include/hw/s390x/" are listed under the "S390 Machines" > part. > > Maybe you would like to list the following files separately here: > hw/s390x/s390-ccw.c > hw/s390x/s390-ccw.h Yes, that makes sense. But seeing the path name here: Should s390-ccw.h rather go into include/hw/s390x/ (even if hw/s390x/ already contains several .h files...)? > > > > > I will likely take any vfio-ccw changes together with the other code I > > take through s390-next. I'll add the respective line when I apply. > Ok. Leave this to you. :> > > > > > > + > > > vhost > > > M: Michael S. Tsirkin <mst@xxxxxxxxxx> > > > S: Supported > > > -- To unsubscribe from this list: send the line "unsubscribe linux-s390" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
