On Thu, Feb 28, 2019 at 10:16:57PM +0530, Aarushi Mehta wrote: > Signed-off-by: Aarushi Mehta <mehta.aar...@gmail.com> > Reviewed-by: Eric Blake <ebl...@redhat.com> > > Note that since thunking occurs throughout the lifetime of the QEMU > instance, there is no matching 'free' to correct. > > ---
Hi Aarushi, The following formatting is commonly used: Subject: [PATCH v3] thunk: fix of malloc to g_new Note that since thunking occurs throughout the lifetime of the QEMU instance, there is no matching 'free' to correct. Signed-off-by: Aarushi Mehta <mehta.aar...@gmail.com> Reviewed-by: Eric Blake <ebl...@redhat.com> I changed the subject to include the prefix of the component being modified. You can look up the preferred prefix using "git log thunk.c" to see what other commits have used. The Signed-off-by: goes at the bottom of the commit description. Don't worry if it takes a few tries to get the formatting conventions. There is scripts/checkpatch.pl for scanning patches for coding style violations but I think it wouldn't have detected these things. The code change itself looks good: Reviewed-by: Stefan Hajnoczi <stefa...@redhat.com>
signature.asc
Description: PGP signature
