On Thu, Jan 08, 2015 at 05:04:20PM +0000, KY Srinivasan wrote: > > > > -----Original Message----- > > From: Vitaly Kuznetsov [mailto:vkuznets@xxxxxxxxxx] > > Sent: Thursday, January 8, 2015 8:02 AM > > To: KY Srinivasan > > Cc: gregkh@xxxxxxxxxxxxxxxxxxx; devel@xxxxxxxxxxxxxxxxxxxxxx; Haiyang > > Zhang; linux-kernel@xxxxxxxxxxxxxxx > > Subject: Re: [PATCH 0/5] Tools: hv: fix compiler warnings and do minor > > cleanup > > > > KY Srinivasan <kys@xxxxxxxxxxxxx> writes: > > > > >> -----Original Message----- > > >> From: devel [mailto:driverdev-devel-bounces@xxxxxxxxxxxxxxxxxxxxxx] > > >> On Behalf Of gregkh@xxxxxxxxxxxxxxxxxxx > > >> Sent: Wednesday, December 10, 2014 6:48 AM > > >> To: Vitaly Kuznetsov > > >> Cc: devel@xxxxxxxxxxxxxxxxxxxxxx; Haiyang Zhang; linux- > > >> kernel@xxxxxxxxxxxxxxx > > >> Subject: Re: [PATCH 0/5] Tools: hv: fix compiler warnings and do > > >> minor cleanup > > >> > > >> On Wed, Dec 10, 2014 at 10:22:40AM +0100, Vitaly Kuznetsov wrote: > > >> > Dexuan Cui <decui@xxxxxxxxxxxxx> writes: > > >> > > > >> > >> -----Original Message----- > > >> > >> From: Vitaly Kuznetsov [mailto:vkuznets@xxxxxxxxxx] > > >> > >> Sent: Tuesday, December 9, 2014 23:48 PM > > >> > >> To: KY Srinivasan > > >> > >> Cc: Haiyang Zhang; devel@xxxxxxxxxxxxxxxxxxxxxx; linux- > > >> > >> kernel@xxxxxxxxxxxxxxx; Dexuan Cui > > >> > >> Subject: [PATCH 0/5] Tools: hv: fix compiler warnings and do > > >> > >> minor cleanup > > >> > >> > > >> > >> When someone does 'make' in tools/hv/ issues appear: > > >> > >> - hv_fcopy_daemon is not being built; > > >> > >> - lots of compiler warnings. > > >> > >> > > >> > >> This is just a cleanup. Compile-tested by myself on top of > > >> > >> linux- > > >> next/master. > > >> > >> > > >> > >> Piggyback this series and send "[PATCH 5/5] Tools: hv: do not > > >> > >> add redundant '/' > > >> > >> in hv_start_fcopy()" > > >> > >> > > >> > >> Vitaly Kuznetsov (5): > > >> > >> Tools: hv: add mising fcopyd to the Makefile > > >> > >> Tools: hv: remove unused bytes_written from kvp_update_file() > > >> > >> Tools: hv: address compiler warnings for hv_kvp_daemon.c > > >> > >> Tools: hv: address compiler warnings for hv_fcopy_daemon.c > > >> > >> Tools: hv: do not add redundant '/' in hv_start_fcopy() > > >> > >> > > >> > >> tools/hv/Makefile | 4 ++-- > > >> > >> tools/hv/hv_fcopy_daemon.c | 10 ++-------- > > >> > >> tools/hv/hv_kvp_daemon.c | 29 +++++++++++++---------------- > > >> > >> 3 files changed, 17 insertions(+), 26 deletions(-) > > >> > >> > > >> > >> -- > > >> > >> 1.9.3 > > >> > > > > >> > > Hi Vitaly, > > >> > > Thanks for the patchset! > > >> > > > > >> > > Acked-by: Dexuan Cui <decui@xxxxxxxxxxxxx> > > >> > > > > >> > > PS, I added Greg into the TO list. > > >> > > The hv code in drivers/hv/ and tools/hv/ usually has to go into > > >> > > Greg's tree first. > > >> > > > >> > Well, I don't mind spamming Greg but he's not on the > > >> > scripts/get_maintainer.pl output. In case he's not monitoring the > > >> > list for patches by some other tool (patchwork?) a patch adding him > > >> > to MAINTAINERS would do the job. > > >> > > > >> > Greg, do you want to become an official Hyper-V maintainer in > > >> > MAINTAINERS? I can send a patch then :-) > > >> > > >> No. It's up to the "real" maintainers to take the patches and then > > >> forward them on to me for inclusion in the kernel tree. KY knows this... > > > > > > I will take care of this. > > > > > > > Hi KY, > > > > I just found out these patches never made it to any repo, at least I can't see > > them in char-misc-next. Do I need to resend? > > Greg, > > I have signed off on these patches. Do you want us to resend them. On a different note, I too have a > Few patches that I sent some weeks ago. Should I be resending them as well. Please resend everything, there has been a mess of different patches and discussions and I can't figure out what should be applied and what should not. I'll guess at a few easy ones, but getting the "correct" ones from you is the best thing. thanks, greg k-h _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel